using-spec-driver

What problem does it solve?

It prevents spec-driven work from starting “half-routed” by forcing you to choose the governing spec-driver workflow skill before you inspect, plan, or implement anything substantive.

Core Features & Use Cases

• Mandatory workflow routing: Ensures tasks are handled by the correct governing skill based on what artefacts (doctrine, delta, design revision, plan/phase sheets) are involved.
• Guardrails against premature work: Blocks file inspection, command execution, and implementation until routing decisions are made.
• Artefact-aware progression: Guides you through the correct order (e.g., routing to /preflight, /scope-delta, /draft-design-revision, /plan-phases, and only then to execution and close-out) so you don’t treat incomplete governance as ready to implement.
• Use Case: When you want to change or explain a spec-driver entity or CLI usage, you route to the /spec-driver skill; when you’re uncertain or need local correctness, you route to /retrieving-memory or /doctrine first.

Quick Start

Use the governing routing process by selecting the appropriate skill path for your task before inspecting files or starting any implementation.