Spec-Driven Development

Overview

Think First, Prompt Second. Enforces a structured 5-phase cycle that prevents vibe coding: Analyze -> Plan -> Ask -> Execute -> Review. Every implementation starts from a spec, respects existing codebase patterns, and delivers small, reviewable, committed phases.

When to Use

• Feature implementation from a spec or requirements doc
• Multi-phase work spanning multiple files or architectural layers
• Any task where "just start coding" leads to drift, over-scoping, or pattern violations

Do NOT use for: single-line fixes, typos, config changes, pure research, or tasks with very specific line-level instructions. If the user asks a direct question or gives a specific fix, respond directly — don't invoke this workflow.

Required Input