By joestump
Drive development from specifications by creating ADRs, writing spec documents, breaking specs into tracker issues, auditing code for spec compliance, and generating Docusaurus documentation. Automatically manage PR reviews and merge workflows.
Create a new Architecture Decision Record (ADR) using MADR format. Use when the user wants to document an architectural decision, says "create an ADR", "we need an ADR for", or discusses a decision that should be recorded.
Comprehensive audit of design artifact alignment across the project. Use when the user says "audit the architecture", "full drift report", or wants a thorough review of spec compliance and ADR adherence.
Quick-check code against ADRs and specs for drift. Use when the user says "check for drift", "does this match the spec", or wants a fast alignment check on a specific file or directory.
Discover implicit architectural decisions and spec-worthy subsystems in an existing codebase. Use when the user says "discover architecture", "what decisions exist in this code", "bootstrap ADRs", or wants to reverse-engineer design artifacts from code.
Generate a documentation site from your ADRs and specs. Use when the user says "generate docs", "create a docs site", or wants to publish their architecture decisions.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for architecture governance: ADRs, specifications, sprint planning, parallel implementation, code review, and documentation generation.
| Skill | Invoke | Description |
|---|---|---|
| ADR | /sdd:adr [description] [--review] | Create an ADR using MADR format with Mermaid diagrams |
| Spec | /sdd:spec [capability] [--review] | Create spec.md + design.md with RFC 2119 requirements and Mermaid diagrams |
| Init | /sdd:init | Set up CLAUDE.md with architecture context for design-aware sessions |
| Prime | /sdd:prime [topic] | Load ADR and spec context into the session, optionally filtered by topic |
| Check | /sdd:check [target] | Quick-check code against ADRs and specs for drift |
| Audit | /sdd:audit [scope] [--review] [--scrum] | Comprehensive drift audit; use --scrum for team-triaged findings grouped into prioritized remediation themes |
| Docs | /sdd:docs [project name] | Generate docs with scaffold/integration modes and manifest-based upgrades |
| List | /sdd:list [adr|spec|all] | List all ADRs and specs with their status |
| Discover | /sdd:discover [scope] | Discover implicit architecture from an existing codebase |
| Plan | /sdd:plan [spec-name or SPEC-XXXX] [--scrum] [--review] [--project <name>] [--no-projects] [--branch-prefix <prefix>] [--no-branches] | Break a spec into trackable issues; use --scrum for a full team-groomed ceremony with spec audit, multi-agent grooming, and automatic organize + enrich |
| Organize | /sdd:organize [SPEC-XXXX or spec-name] [--project <name>] [--dry-run] | Retroactively group existing issues into tracker-native projects |
| Enrich | /sdd:enrich [SPEC-XXXX or spec-name] [--branch-prefix <prefix>] [--dry-run] | Add branch naming and PR conventions to existing issue bodies |
| Work | /sdd:work [SPEC-XXXX | issue numbers | (empty = propose from backlog)] [--max-agents N] [--draft] [--dry-run] [--no-tests] [--module <name>] | Pick up tracker issues and implement them in parallel using git worktrees |
| Review | /sdd:review [SPEC-XXXX or PR numbers] [--pairs N] [--no-merge] [--dry-run] [--module <name>] | Review and merge PRs using reviewer-responder agent pairs |
| Respond | /sdd:respond [PR numbers or URL | (empty = infer from current branch)] [--reply-only] [--fix-only] [--no-push] [--dry-run] [--module <name>] | Address review feedback on a PR: make the code fixes, push, and reply to each thread |
| Status | /sdd:status [ID] [status] | Change the status of an ADR or spec |
| Graph | /sdd:graph <verb> [<artifact-id>] [--scope <subtree>] [--module <name>] [--table|--mermaid|--json] | Build and query the artifact graph: validate, impact, ancestors, chain, orphans, cycles, backfill. ASCII DAG default; --json is the stable contract for downstream consumers |
Add to your project's .claude/settings.json:
{
"extraKnownMarketplaces": {
"claude-plugin-sdd": {
"source": {
"source": "github",
"repo": "joestump/claude-plugin-sdd"
}
}
},
"enabledPlugins": {
"sdd@claude-plugin-sdd": true
}
}
Then restart Claude Code. The plugin's skills will be available as /sdd:init, /sdd:prime, /sdd:adr, /sdd:spec, /sdd:plan, /sdd:organize, /sdd:enrich, /sdd:work, /sdd:review, /sdd:respond, /sdd:check, /sdd:audit, /sdd:discover, /sdd:docs, /sdd:list, /sdd:status, /sdd:graph, /sdd:index, /sdd:search, and /sdd:report-friction.
All configuration lives in your project's CLAUDE.md under a ### SDD Configuration section. No separate JSON config files are needed -- skills read and write configuration as markdown, keeping everything in one place.
Run /sdd:init to set up the initial configuration, or add it manually:
### SDD Configuration
#### Tracker
- **Type**: github
- **Owner**: your-org
- **Repo**: your-project
#### Branch Conventions
- **Enabled**: true
- **Prefix**: feature
- **Epic Prefix**: epic
- **Slug Max Length**: 50
#### PR Conventions
- **Enabled**: true
- **Close Keyword**: Closes
- **Ref Keyword**: Part of
- **Include Spec Reference**: true
#### Worktrees
- **Base Dir**: .claude/worktrees/
- **Max Agents**: 4
- **Auto Cleanup**: false
- **PR Mode**: ready
#### Review
- **Max Pairs**: 2
- **Merge Strategy**: squash
- **Auto Cleanup**: false
#### Projects
- **Default Mode**: per-epic
- **Views**: All Work, Board, Roadmap
- **Columns**: Todo, In Progress, In Review, Done
- **Iteration Weeks**: 2
All sections and keys are optional. Missing keys use sensible defaults. The tracker preference is saved automatically when you first use /sdd:plan.
Two additional top-level keys control parallel agent behavior:
## SDD Configuration
- **Max parallel agents**: 4
- **Hotspot threshold**: 50%
npx claudepluginhub joestump/claude-plugin-sdd --plugin sddA collection of reusable Claude skills by Joe Stump.
GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding
Spec-driven development methodology for full-stack teams
Spec-Driven Development (SDD) plugin for Claude Code providing a comprehensive workflow for building features with requirements, design, tasks, and implementation phases.
Specification-Driven Development with Process Discipline for Claude Code
Specification-driven development workflow: specify → plan → tasks → implement
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.