executing-plans

Topics in the source

• Executing Plans
• Overview
• The Process
• Step 1: Load and Review Plan
• Step 2: Execute Batch
• Step 3: Report
• Step 4: Continue
• Step 5: Complete Development

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." 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 Default: First 3 tasks For each task: 1. Mark as inprogress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed When batch complete: Show what was implemented Show verification output Say: "Ready for feedback." Based on feedback: Apply changes if needed Execute next batch Repeat until complete 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 STOP executing immediately when: Hit a blocker mid-batch (missing dependency, test fails, instruction unclear) Plan has critical gaps prev

This is an excerpt. Refer to the complete source and its current requirements.