executing-plans

# executing-plans ## Structured-artifact format boundary New full-lane workflows default to HTML through the installed engine. Existing HTML pairs use the same path. Load [includes/artifacts.md](../../includes/artifacts.md) before HTML artifact I/O; its typed identity, binding, receipt, contextual-read, and scope-state rules replace rendered-document parsing and direct status-cell edits. Existing authoritative Markdown pairs stay on their exact legacy path without conversion. A missing, invalid, or unqualified HTML capability must fail closed rather than fall back to new Markdown authority. HTML `--farm` dispatch remains disabled. Keep every other workflow gate, including human checkpoints, unchanged. 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. An HTML checkpoint is an acceptance scope, not a new user checkpoint in `/sprint`. Sprint routes directly to `subagent-driven-development` and does not inherit this attended coordinator's pauses. ## Pre-flight Read these, or STOP and surface the gap — never guess a path, a command, or a task boundary: - The discovered authoritative spec/plan pair. Existing Markdown pairs retain their current ledger...