Executing Plans

Overview

The Process

Step 1: Load and Review Plan

.claude/plans/<plan-id>/

1. Read orchestration plan at

   plan.md

   and manifest at

   manifest.json

2. For each task in the current batch, read its briefing file from

   briefings/task-NN.md

3. Only load briefings for the current batch (default 3), not all tasks at once
4. Review critically — identify any questions or concerns about the plan
5. If concerns: Raise them with your human partner before starting
6. If no concerns: Create TodoWrite and proceed

docs/plans/*.md

1. Read the plan file directly
2. Follow the same review and batch process below

manifest.json

.md

.claude/plans/

docs/plans/

.md

Step 2: Execute Batch

1. Mark as in_progress
2. Follow each step exactly (briefing files have bite-sized steps)
3. Run verifications as specified in the briefing's Success Criteria
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 (load next batch's briefing files)
• Repeat until complete

Step 5: Complete Development

1. If using plan directory format, clean up:
   • Optionally write

     .claude/plans/<plan-id>/summary.md

     with execution notes
   • Delete the plan directory:

     rm -rf .claude/plans/<plan-id>/

   • If deletion fails, warn but do not block
2. Announce: "I'm using the finishing-a-development-branch skill to complete this work."
3. REQUIRED SUB-SKILL: Use finishing-a-development-branch
4. 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
• Read briefing files per-batch, not all at once
• 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

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