execute-phase

Spec-driven delta execution requires moving the owning delta from draft to in-progress before coding begins. This lifecycle state transition ensures implementation work stays aligned with validated phase sheet plans and prevents undocumented scope drift.

To maintain traceability during phase execution, enter through a single execution gate, run preflight checks to confirm inputs, capture progress with structured notes, update delta docs, and hand off to verification audit for reconciliation.

Preflight checks are required before coding in spec-driven development to surface confirmed inputs, unresolved design questions, and policy tensions. They ensure implementation begins only when assumptions are validated and ambiguities are addressed.

Stop the delta implementation workflow immediately and use a consultation command to resolve the ambiguity. This blocker-first approach prevents implementation drift when preflight or execution reveals unresolved design or policy tensions.

No, spec-driven execution requires an active phase sheet along with design records and implementation plans. The workflow reads these inputs during preflight to enforce gated entry and validate lifecycle state transitions before coding begins.

Gated lifecycle execution mandates strict sequential progression, preventing ad-hoc coding outside spec-driven development. You cannot skip the draft to in-progress transition, preflight checks, or audit handoff, limiting rapid prototyping without structured phase sheets.