Spec Driven Development

Use when planning or implementing any non-trivial TicketPilot change. Requires proposal, design, tasks, acceptance criteria, and validation before implementation.

lennney 9e2aa1d 552 B Updated

File contents

Spec-driven Development

Rules:

  1. Do not implement non-trivial features without a spec/change.
  2. Every change must include objective, scope, non-goals, affected modules, acceptance criteria, and test plan.
  3. Implementation must follow tasks.md.
  4. Completed tasks must be checked off.
  5. After implementation, run the quality gate.

lennney/ticketpilot/tree/main/.claude/skills/spec-driven-development commit 9e2aa1d8a5

Frequently asked questions

npx skillmds@latest add lennney/spec-driven-development