Spec-driven development

When to use

• New feature, project, or significant change
• Requirements ambiguous or multi-file scope
• Architectural decision needed before code

When not to use

• Single-line fixes, typos, obvious one-file changes

Gated workflow

SPECIFY -> PLAN -> TASKS -> IMPLEMENT

Do not implement until spec (or explicit assumptions) is agreed.