executing-plans

Automation & Intégrations

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Documentation

Executing Plans

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

Announce at start: "I'm using the executing-plans skill to implement this plan."

The Process

Step 1: Load and Review Plan

1.Read plan file
2.Review critically - identify any questions or concerns about the plan
3.If concerns: Raise them with your human partner before starting
4.If no concerns: Create TodoWrite and proceed

Step 2: Execute Batch

Default: First 3 tasks

For each task:

1.Mark as in_progress
2.Follow each step exactly (plan has bite-sized steps)
3.Run verifications as specified
4.Mark as completed

Step 3: Report

When batch complete:

●Show what was implemented
●Show verification output
●Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

●Apply changes if needed
●Execute next batch
●Repeat until complete

Step 5: Complete Development

After all tasks complete and verified:

●Announce: "I'm using the finishing-a-development-branch skill to complete this work."
●REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
●Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

STOP executing immediately when:

●Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
●Plan has critical gaps preventing starting
●You don't understand an instruction
●Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

●Partner updates the plan based on your feedback
●Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

●Review plan critically first
●Follow plan steps exactly
●Don't skip verifications
●Reference skills when plan says to
●Between batches: just report and wait
●Stop when blocked, don't guess

Compétences similaires

Explorez d'autres agents de la catégorie Automation & Intégrations

Voir tout le catalogue

asana-automation

"Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas."

VOIR LA FICHE

zapier-make-patterns

"No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power "

VOIR LA FICHE

conductor-validator

Validates Conductor project artifacts for completeness,

VOIR LA FICHE
Utiliser l'Agent executing-plans - Outil & Compétence IA | Skills Catalogue | Skills Catalogue