executing-plans

# executing-plans Coordinate the plan in small, user-acknowledged batches. Routed to by `/feature` after `writing-plans` has produced a plan. Each batch is executed by `subagent-driven-development` — fresh author agent per task, spec-compliance review, quality review, fresh verification — and the user checkpoints between batches. The orchestrator never implements; it schedules and checkpoints. ## Pre-flight Read these, or STOP and surface the gap — never guess a path, a command, or a task boundary: - `<project-root>/.codearbiter/plans/<slug>.md` — the approved plan. The ordered task list and each task's verification command are the contract. No plan, no execution. - `<project-root>/.codearbiter/specs/<slug>.md` — the spec the plan implements. - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `<project-root>/.codearbiter/tech-stack.md` — the exact verification, test, and build invocations. ## Phase 1 — Batch plan · gate: BLOCK Group the plan's tasks into small batches. Keep batches tight — three to five tasks is a ceiling, not a target. Respect the plan's ordering and dependencies: a task never lands before the task it depends on. **Resume is the normal re-entry.** A task already `ACCEPTED` in the plan's status column was verified before an earlier interruption — exclude it from batching and say so ("resuming: T-01–T-03 already ACCEPTED"). Batch only the non-`ACCEPTED` tasks, starting at the first. Never re...