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/other-templates.md
View on GitHub# Other Spec Templates
## Template: Domain Definition
```markdown
---
title: [Definition Name]
spec_type: tech
status: active
domain: [Domain]
issue: [PROJ-XXX]
created: YYYY-MM-DD
updated: YYYY-MM-DD
sdd_version: [X.Y.Z]
---
# Definition: [Definition Name]
## Description
[What this definition represents in the domain]
## Properties
| Property | Type | Required | Description |
|----------|------|----------|-------------|
| id | UUID | Yes | Unique identifier |
| name | string | Yes | Display name |
| createdAt | DateTime | Yes | Creation timestamp |
## Relationships
- **[Related Definition]**: [Relationship description]
## Business Rules
1. [Rule about this definition]
2. [Another rule]
## Lifecycle
[States this definition can be in and transitions between them]
```
## Template: Product Spec (External Input)
Product specs are external inputs archived for reference. They focus on WHAT and WHY, not HOW.
```markdown
---
title: [Product Spec Name]
spec_type: product
status: active
domain: [Domain Name]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
# [Product Spec Name]
## Overview
[What this product/feature does and why it matters to users]
## User Stories
### [User Group]
- As a [role], I want [capability] so that [benefit]
## Requirements
### Functional Requirements
- [Requirement 1]
- [Requirement 2]
### Non-Functional Requirements
- [Performance, security, scalability requirements - often missing]
## Acceptance Criteria
- [Criterion 1]
- [Criterion 2]
## UI/UX Specifications
[Visual designs, mockups, user flows - typically well-specified in product specs]
## Out of Scope
- [What this product spec explicitly does NOT cover]
```
**Note:** Product specs are typically incomplete:
- Rich in user-facing interface details
- Sparse on business logic, contracts, and data layer details
- Missing edge cases and error handling
- Implicit assumptions not documented
The transformation process identifies these gaps and asks clarifying questions.
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 |