Executing Plans

After all tasks complete and verified:

• 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 when:

• Hit blocker (missing dependency, test fails, instruction unclear)
• Plan has critical gaps preventing start
• 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:

• Calum updates plan based on 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:

• superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
• superpowers:writing-plans - Creates plan this skill executes
• superpowers:finishing-a-development-branch - Complete development after all tasks