Spec-Driven Development Workflow

Step 1: Spec Lookup

Check for an existing spec:

• PRs: docs/specs/history/prs/YYYY-MM/PR-<number>.md
• Bugs: docs/specs/bugs/ledger.md
• Baseline: docs/specs/baseline/<capability>/

If no spec exists, tell the user and create one from the template at docs/specs/templates/pr-spec.md.

Step 2: Ambiguity Check

Evaluate the request:

• Expected behavior is defined with concrete inputs/outputs
• Error cases and edge cases are specified
• Scope is clear — which files change, which don't
• There is only one reasonable implementation approach