kienbui1995 Executing Plans
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: If subagents are available, use magic-powers:subagent-driven-development instead — higher quality through fresh context per task.
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically — identify questions or concerns
- If concerns: raise with user before starting
- If no concerns: create TodoWrite 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
- Use magic-powers:verification-before-completion before marking done
- Mark as completed
Step 3: Complete Development
After all tasks verified:
- Use magic-powers:finishing-a-development-branch
- Verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker (missing dependency, test fails, unclear instruction)
- 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:
- User 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
- Stop when blocked, don't guess
- Never start implementation on main/master without explicit user consent
Integration
Required workflow skills:
- magic-powers:using-git-worktrees — set up isolated workspace before starting
- magic-powers:writing-plans — creates the plan this skill executes
- magic-powers:finishing-a-development-branch — complete development after all tasks
- magic-powers:verification-before-completion — verify before claiming done