Prioritizes documentation, architecture decisions, and risk assessment before writing code.
Install
mkdir -p .claude/skills/sdd && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12822" && unzip -o skill.zip -d .claude/skills/sdd && rm skill.zipInstalls to .claude/skills/sdd
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Structured/spec-driven development process for documentation-first work.Key capabilities
- →Produce documentation-first outputs
- →Generate specs, decisions, and tickets
- →Prefer Markdown outputs under `/docs`
- →Prepare Notion-ready outputs
- →Include context, assumptions, decisions, trade-offs, risks, and next actions in outputs
- →Link to related documentation
How it works
The skill enforces a documentation-first approach by requiring specs, decisions, and tickets before application code, and mandates specific quality attributes for all outputs.
Inputs & outputs
When to use sdd
- →Write technical specifications
- →Assess project risks
- →Document architectural decisions
About this skill
Skill: sdd
Purpose
Structured/spec-driven development process for documentation-first work.
Project rules
- Follow
AGENTS.md. - Do not write application code unless this skill is used from an implementation workflow.
- Documentation-first: produce docs, decisions and tickets before code.
- Prefer Markdown outputs under
/docs. - Prepare Notion-ready outputs when the workflow requests it.
Required output quality
Every output must include:
- context
- assumptions
- decisions
- trade-offs
- risks
- next actions
- links to related docs when applicable
Default destination
Use the destination defined by the active workflow.
When not to use it
- →When writing application code directly without an implementation workflow
- →When documentation is not the primary focus
- →When outputs do not require detailed quality attributes
Limitations
- →Does not write application code unless used from an implementation workflow
- →Requires outputs to include context, assumptions, decisions, trade-offs, risks, and next actions
- →Prefers Markdown outputs under `/docs`
How it compares
This skill formalizes a documentation-first development process, ensuring that all work is preceded by detailed documentation and decision-making, unlike a code-first approach.
Compared to similar skills
sdd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sdd (this skill) | 0 | 3mo | No flags | Intermediate |
| architecture-decision-records | 54 | 5mo | Review | Beginner |
| wiki-architect | 11 | 3mo | No flags | Advanced |
| smart-docs | 4 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
architecture-decision-records
wshobson
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
smart-docs
sopaco
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.
codebase-documenter
mhattingpete
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
c4-architecture-c4-architecture
sickn33
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
dagger-design-proposals
dagger
Write design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.