2.4 KiB
| name | description |
|---|---|
| executing-plans | Execute an already-written implementation plan document task by task, with verification and review checkpoints between steps. Use when a plan.md or spec already exists and the work now needs carrying out, including knowing when to stop and ask for help versus revisit earlier steps. Triggers: execute the plan, work through the plan, implement the plan, start on the plan, next task in the plan, follow the spec. Pairs with writing-plans and subagent-driven-development. |
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Note: this works much better with subagent support. If subagents are available in this environment, prefer the subagent-driven-development skill instead of this one.
The Process
Step 1: Load and Review Plan
- Read the plan file
- Review critically — identify questions or concerns
- If concerns: raise them with your human partner before starting
- If none: create todos for the plan items and proceed
Step 2: Execute Tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Step 3: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- Use the finishing-a-development-branch skill: verify tests, present options, execute choice.
When to Stop and Ask for Help
STOP executing immediately when: you hit a blocker (missing dependency, test fails, instruction unclear), the plan has critical gaps preventing starting, you don't understand an instruction, or verification fails repeatedly. Ask for clarification rather than guessing.
When to Revisit Earlier Steps
Return to Step 1 review when the partner updates the plan based on feedback, or the 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 other skills when the plan says to. Stop when blocked, don't guess. Never start implementation on main/master branch without explicit user consent.
Integration
Related skills: using-git-worktrees (isolated workspace), writing-plans (creates the plan this executes), finishing-a-development-branch (completes development after all tasks).