From sdd
Provides templates, schemas, validation, and Git workflow guidelines for product and tech SPEC.md files with acceptance criteria.
npx claudepluginhub liorcohen/sdd --plugin sddThis skill uses the workspace's default tool permissions.
Use templates below as starting points.
Creates 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.
Generates product specifications via collaborative interview with web research and codebase analysis. Lists, creates, and revises specs saved as Markdown in .otto/specs for planning, requirements, and feature design.
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.
Share bugs, ideas, or general feedback.
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: