Menu
Templates and validation for writing product specifications.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Orchestrates SDD project initialization — version detection, environment verification, scaffolding, and git setup.
Manage project settings in sdd/sdd-settings.yaml including component settings that drive scaffolding.
Single gateway for all core↔tech-pack interactions. Reads manifests, resolves paths, loads skills/agents, routes commands.
Manage tasks and plans using the .tasks/ directory.
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
Standards for authoring SDD plugin commands — frontmatter, user interaction, skill/agent invocation, CLI integration, and output formatting.
| name | spec-writing |
| description | Templates and validation for writing product specifications. |
| user-invocable | false |
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: