executing-plans

Executing Plans

Execute a plan continuously in TDD, then review.

Announce: "I'm using the executing-plans skill to implement this plan."

The Rule

Every task follows @tdd: RED → GREEN → REFACTOR
No production code without a failing test first.

Prerequisites

• Plan exists in docs/plans/YYYY-MM-DD-<topic>.md
• On a feature branch

The Flow

Verify Branch → EC Search → Load Plan → Execute Tasks → Review → Finish

Step 1: Verify Branch

git branch --show-current

Must be on a feature branch, not main.

Step 2: Load Context

Get project config and relevant context:

ec_search:
  query: project config
  type: config

ec_search:
  query: [feature area]
  type: pattern

ec_search:
  query: [feature area]
  type: learning

Note any gotchas or patterns that apply to this implementation.

Step 3: Load and Review Plan

1. Read the plan file
2. Choose ONE progress tracking approach (don't mix):
   • Tasks (preferred): If TaskCreate/TaskUpdate tools are available, use Tasks. Creates persistent, shareable progress.
   • TodoWrite (fallback): If Tasks aren't available, use TodoWrite for the session.
3. If concerns about the plan, raise them before starting

Important: Pick one approach and stick with it for the entire execution. Don't mix Tasks and TodoWrite.

Option A: Using Tasks (Preferred)

If TaskCreate/TaskUpdate/TaskList tools are available, create one task per plan task:

TaskCreate: "Task 1: [first task summary]"
TaskCreate: "Task 2: [second task summary]" → addBlockedBy: [task 1 id]
... one per plan task, chained in order

Benefits:

• Progress survives context switches and session restarts
• Subagents can share the same task list with CLAUDE_CODE_TASK_LIST_ID
• Dependencies prevent out-of-order execution

Option B: Using TodoWrite (Fallback)

If Tasks aren't available, create a TodoWrite with all plan tasks and update as you go.

Step 4: Execute the Plan

Execute continuously — work through every task in order, stopping only for a real blocker (see "When to Stop"). Do not pause for feedback between tasks; that round-trip adds latency without improving quality.