using-spec-driver

Spec-driven development prevents premature execution by enforcing mandatory routing to a governing workflow skill, blocking file inspection and implementation until required delta, design, and plan artefacts exist.

The correct spec-driver workflow progression routes tasks through preflight, scope-delta, draft-design-revision, and plan-phases sequentially, ensuring governance artefacts are completed before execution and close-out phases begin.

You need to route tasks to a governing workflow skill before planning whenever creating, editing, finding, explaining, executing, or closing spec-driver artefacts, especially when the correct next phase is uncertain.

Spec-driven workflows block command execution by requiring routing decisions up front, preventing inspection and implementation until mandatory delta, design, plan, and phase artefacts are created and validated.

No, spec-driven development guardrails block file inspection until you select the appropriate governing skill, ensuring tasks involving CLI-driven workflows and artefact changes are properly routed before any substantive work begins.

Spec-driven development requires routing to doctrine or retrieving-memory skills first when you need local correctness or are uncertain about the governing path, ensuring proper context before proceeding with spec-driver entity changes.