Stats
Actions
Tags
From sdd
Provides templates, schemas, validation, and Git workflow guidelines for product and tech SPEC.md files with acceptance criteria.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdd:spec-writingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use templates below as starting points.
Use templates below as starting points.
Schema: schemas/input.schema.json
Accepts spec type, change type, title, domain, and optional issue reference.
Schema: schemas/output.schema.json
Returns complete SPEC.md markdown and validation results for required fields, sections, and format.
Product Specs (external input):
spec_type: productTech Specs (generated SPEC.md files):
spec_type: techGit is the state machine:
active, deprecated, superseded, archived| Type | Location |
|---|---|
| Change specs | changes/YYYY/MM/DD/<change-name>/SPEC.md |
| Implementation plans | changes/YYYY/MM/DD/<change-name>/PLAN.md |
| Domain definitions | specs/domain/definitions/<definition-name>.md |
| API contracts | specs/architecture/api-contracts.md |
Date-based organization:
Always use Given/When/Then:
- [ ] **AC1:** Given [precondition], when [action], then [expected result]
For detailed guidance, read these on-demand:
npx claudepluginhub liorcohen/sdd --plugin sddCreates or updates SPEC.md documents from requirements, notes, or interview output, structuring into sections for goals, design, edge cases, security, testing, and success criteria. Use for feature specs.
Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.