execute-plan

Execute Plan

Overview

Load plan, review critically, execute ready tasks in waves in the ticket venue (this checkout if already on the ticket branch, else a worktree), run the verifications the plan specifies, report when complete.

Announce at start: "I'm using the execute-plan skill to implement this plan."

Invariants — read first, re-read after any context compaction

• Review the plan critically first.
• Follow plan steps exactly; don't skip verifications.
• Commit with explicit paths only (or the repo's commit helper); never git add ..
• Stop when blocked — don't guess.
• Execute in this checkout when already on the ticket branch; otherwise in the ticket worktree. The venue's plan copy is the live one.
• Dispatch every legal task in a wave; fan in serially — commit, sync docs, tick, one task at a time.
• This skill runs the review gate as Step 4.4. Do not also invoke /thermo-nuclear-code-quality-review unless the user edited code after Verdict: ship. /graph-retro is post-merge, not the next implement step.
• Long runs get compacted; this file and the plan live on disk. If the conversation was summarized, or you cannot recall a rule verbatim, re-read this file and the plan header's For agentic workers block before the next action — never act from a summary of them.

The Process

Step 1: Load and Review Plan

1. Read the plan file (the one produced by write-plan or interview-plan). Infer <TICKET-ID> from the plan path first, then an existing ticket worktree, then the current branch, then ask once — the user's checkout may be on main or another ticket. If the user did not say which file, search in this order:
   • already-listed worktree for this ticket (it is live — prefer it)
   • docs/features/<TICKET-ID>/ (tracked)
   • docs/plans/<TICKET-ID>/ (gitignored WIP)
   • Legacy flat docs/plans/*.md or docs/PLAN_*.md If both tracked and WIP copies exist in the same checkout, diff them; if they diverge, ask which is active — never silently prefer the promoted copy over newer WIP. Record the absolute path of the user's checkout — Step 2 copies from there only when the worktree does not already have the WIP docs.
2. Review it critically — identify any questions, gaps, or concerns before touching code. A plan whose header links a spec but carries no **Audit:** clean line: if an interview spec exists for this ticket, the Audit Pass was interrupted — confirm before executing. If there was no interview (standalone write-plan), missing audit is expected — still confirm once, then proceed. Do not treat both cases as "interrupted interview".
3. If concerns: raise them with the user before starting. Resume / stash / TodoWrite wait until Step 2 has the live plan.