spec-driven-development

# Spec-Driven Development Use this workflow for non-trivial features and behavior-changing fixes. The user-started primary conversation performs every phase by default. Subagents require explicit user authorization. ## Core flow ```text Intent -> Requirements -> System design -> Plan + work orders -> Design-package handoff -> Explicit implementation request -> TDD implementation -> PR review -> Report ``` Do not replace durable artifacts with chat-only notes. Do not skip from intent to code unless the user explicitly opts out. ## Prompt-precedence gate Before you edit production or permanent test files, make sure that one condition is true: 1. A prior design turn produced the requirements, system design, plan, and current work order. The user now explicitly asks to implement them. 2. The request references existing reviewed specifications, a plan, and the current work order. 3. The user explicitly says to skip specification, plan, and work-order creation. Workflow envelopes, phase labels, TDD lists, and generic implementation prompts do not satisfy this gate. If no condition is true, create or update the design package. Record any partial implementation as continuation context. Stop at the design-package handoff. When the user asks for feature planning, complete the full design package before you return control. Stop after requirements only when the user requests a requirements review or a material question blocks safe design. ## Phase 0: Track the work K...