git:20260912.8ebef00 to git:20260920.677b300

2 added, 2 removed. Audit A to A.

---

- name: Spec-Driven Development

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

+ name: spec-driven-dev

+ description: Contract-first development, proportional spec routing and planning. Use for spec driven work (SDD) - writing a specification, capturing requirements, or applying the issue contract.

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/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