execute-phase

Execute Phase

Resume a multi-session project by reading the plan state, executing the next phase, and maintaining context continuity. The human is present — confirm scope before executing, ask when blocked.

Step 1 — Orient (Read Plan State)

Read these files in order:

1. CLAUDE.md — Project identity, current state, key files, commands
2. .plan/PLAN.md — Find the current phase and next uncompleted item
3. .plan/MEMORY.md — Absorb all shared context, decisions, gotchas
4. .plan/DRIFT.md — Check for any spec changes since last session
5. .agents/CONVENTIONS.md — Build patterns and rules (if exists)

Then state clearly:

📍 Current Phase: {N} — {Name}
📋 Next Item: {N.X} — {Description}
📝 Items remaining in phase: {count}
⚠️  Gotchas to watch: {any relevant from MEMORY.md}

Step 2 — Plan the Session

Before writing any code, state:

• What items you will tackle this session
• Any open questions that need resolving first
• Any risks or dependencies

Wait for user confirmation before proceeding.

Step 3 — Execute

Work through items sequentially:

• Complete each item fully before moving to the next
• Test as you go — don't batch all testing to the end
• If you hit a blocker, note it and ask the user
• If something doesn't match the spec, flag it — don't silently diverge
• Follow patterns from MEMORY.md and CONVENTIONS.md

After completing each item, note it:

✅ {N.X} — {Description} — Done

Build Gate

After completing items, run the project's build/verify command:

# Read BUILD_CMD from autopilot.config, or use project defaults
# e.g., bun run typecheck && bun run lint

If the build fails:

• Read the error output
• Fix the issue
• Re-run until it passes
• If stuck, ask the user for help

Step 4 — Check Exit Criteria

When all items in the phase are complete, verify the exit criteria from PLAN.md:

• Run any tests or build commands
• Demonstrate the working functionality
• Confirm with the user