2.0 KiB
2.0 KiB
| name | description |
|---|---|
| executing-plans | Use when you have a written implementation plan to execute in the current session with review checkpoints |
Executing Plans
Overview
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
The Process
Step 1: Load and Review Plan
- Read plan file from
docs/superpowers/plans/ - Review critically — identify any questions or concerns
- If concerns: Raise them with your human partner 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
- Mark as
completed
After each task, run verification:
npm run test # Verify tests pass
npm run lint # Verify lint clean
Step 3: 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 (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.
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 branch without explicit user consent
Integration
Required workflow skills:
- superpowers:using-git-worktrees — REQUIRED: Set up isolated workspace before starting
- superpowers:writing-plans — Creates the plan this skill executes
- superpowers:finishing-a-development-branch — Complete development after all tasks