LiorCohen/sdd / plugin/core/skills/spec-writing
spec-writing
VerifiedTemplates and validation for writing product specifications.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| resources/epic-spec-template.md | markdown | 1.9 KB |
| resources/feature-spec-template.md | markdown | 4.4 KB |
| resources/frontmatter-validation.md | markdown | 3.3 KB |
| resources/other-templates.md | markdown | 2.0 KB |
| schemas/input.schema.json | config | 1.1 KB |
| schemas/output.schema.json | config | 1.3 KB |
resources/epic-spec-template.md
View on GitHub# Epic Spec Template (Tech Spec)
An epic contains multiple feature-type changes. The epic SPEC.md defines the overall goal, and each child change in `changes/` has its own feature SPEC.md.
```markdown
---
title: [Epic Name]
spec_type: tech
type: epic
status: active
domain: [Domain Name]
issue: [PROJ-XXX or GitHub issue URL]
created: YYYY-MM-DD
updated: YYYY-MM-DD
sdd_version: [X.Y.Z]
---
# Epic: [Epic Name]
## Overview
[1-2 sentences: what this epic accomplishes and why it matters]
## Changes
| Change | Description | Dependencies |
|--------|-------------|--------------|
| [change-name] | [What this change does] | None |
| [change-name] | [What this change does] | [depends-on] |
## Acceptance Criteria
### [Capability Group]
- [ ] **AC1:** Given [precondition], when [action], then [result]
- [ ] **AC2:** Given [precondition], when [action], then [result]
## Cross-Cutting Concerns
[Shared patterns, conventions, or constraints that apply across all changes]
## Out of Scope
- [What this epic explicitly does NOT cover]
```
## Epic Child Change Spec
Each child change inside `changes/` uses the standard feature template with one additional frontmatter field:
```yaml
---
title: [Feature Name]
spec_type: tech
type: feature
parent_epic: ../SPEC.md
status: active
domain: [Domain Name]
issue: [PROJ-XXX]
created: YYYY-MM-DD
updated: YYYY-MM-DD
sdd_version: [X.Y.Z]
---
```
The `parent_epic` field links the child back to the epic spec.
## Epic Directory Structure
```text
changes/YYYY/MM/DD/<epic-name>/
├── SPEC.md # Epic-level spec
├── PLAN.md # Epic-level plan (change ordering)
└── changes/
├── <change-name>/
│ ├── SPEC.md # Feature spec
│ └── PLAN.md # Feature plan
└── <change-name>/
├── SPEC.md
└── PLAN.md
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |