Executing Plans

Overview

The Process

Step 1: Load and Review 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

Step 2: Execute Batch

1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed

Step 3: Report

• Show what was implemented
• Show verification output
• Say: "Ready for feedback."

Step 4: Continue

• Apply changes if needed
• Execute next batch
• Repeat until complete

Step 5: Complete Development

• Announce: "I'm using the finishing-a-development-branch skill to complete this work."
• REQUIRED SUB-SKILL: Use software-forge:finishing-a-development-branch
• Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

• Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
• Plan has critical gaps preventing starting
• You don't understand an instruction
• Verification fails repeatedly

When to Revisit Earlier Steps

• Partner updates the plan based on your feedback
• Fundamental approach needs rethinking

Remember

• Review plan critically first
• Follow plan steps exactly
• Don't skip verifications
• Reference skills when plan says to
• Between batches: just report and wait
• Stop when blocked, don't guess
• Never start implementation on main/master branch without explicit user consent

Integration

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