git:20260816.e816052 to git:20260912.8ebef00

9 added, 6 removed. Audit A to A.

---

name: Spec-Driven Development

- description: Specification-first development workflow and planning

- trigger: spec driven, specification, SDD, planning, requirements

+ description: Contract-first development, proportional spec routing, and planning

+ trigger: spec driven, specification, SDD, planning, requirements, issue contract

metadata:

provenance:

class: cpp-authored

---

# Spec-Driven Development Skill

When the user asks about spec-driven development, planning, or requirements:

- 1. Read `docs/skills/spec-driven-dev.md`

- 2. Explain the SDD workflow (Spec → Sandbox → Production)

- 3. Provide the spec template

- 4. Reference GitHub Spec Kit for tooling

+ 1. Read `docs/agents/issue-contract.md` - the canonical contract every change states

+ 2. Route by tier: Tier 1 and Tier 2 express the contract in the issue body; Tier 3

+ escalates to a full `.specify/` spec that the issue references rather than copies

+ 3. Read `docs/skills/spec-driven-dev.md` for the Tier 3 workflow and templates

+ 4. Keep the outcome separate from a proposed approach, and treat a constraint as

+ binding even when its rationale is missing

+ 5. Reference GitHub Spec Kit for tooling