subagent-driven-development

# subagent-driven-development One task, one fresh subagent, two reviews, proof on a fresh run. Routed to by `/sprint` (full plan, autonomous) and by `executing-plans` (one batch at a time, with human checkpoints between batches). The loop processes tasks in dependency order and never trusts a self-report. ## Pre-flight Read these, or STOP and surface the gap — never guess scope, command, or obligation: - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `<project-root>/.codearbiter/plans/<slug>.md` — the approved plan. Each task carries an exact path set and a verification command. This is the task source. - `<project-root>/.codearbiter/specs/<slug>.md` — the approved spec. Each task's obligation traces to it. The spec-compliance review measures against it. - `<project-root>/.codearbiter/tech-stack.md` — build, test, and verification invocations; file layout; the scope-to-author mapping. - `<project-root>/.codearbiter/security-controls.md` — only when a task touches a security boundary (auth, crypto, secrets, a trust boundary). **Optional `scope` parameter:** when invoked by `executing-plans`, a list of task IDs is passed. The loop processes only those tasks (in their internal dependency order). When `scope` is absent (the `/sprint` path), the loop processes the full plan from first unblocked task to last. ## Phase 1 — Task selection · gate: BLOCK Pull the next unblocked task from the plan in dependency orde...