sdd-analyze
01Command Claude Code
Read-only cross-check of spec, plan, and tasks for consistency, duplication, gaps, and constitution violations before implementation starts.
not rated 1 yesterday A 25 tokens
original MIT
1Stars on the repository
105Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
sdd-clarify
02Command Claude Code
Systematically find and resolve the highest-impact ambiguities in a spec before planning starts, instead of discovering them mid-implementation.
not rated 1 yesterday A 25 tokens
original MIT
Command Claude Code
Create or update the project's constitution — the small set of non-negotiable product/architecture principles every spec, plan, and implementation must be checked against.
not rated 1 yesterday A 31 tokens
original MIT
Command Claude Code
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
not rated 1 yesterday A 28 tokens
original MIT
sdd-plan
05Command Claude Code
Turn a clarified spec into a concrete technical plan — architecture, data model, and interfaces — before any task breakdown or code.
not rated 1 yesterday A 25 tokens
original MIT
sdd-specify
06Command Claude Code
Turn a short feature request into a written spec — user-facing behavior and testable acceptance criteria, deliberately free of implementation detail — before any planning starts.
not rated 1 yesterday A 30 tokens
original MIT
sdd-tasks
07Command Claude Code
Turn a plan into an ordered, independently-checkable task list, with every task traceable back to a requirement and every requirement covered by at least one task.
not rated 1 yesterday A 32 tokens
original MIT
evaluate
08Command Claude Code
Pre-deployment evaluation checklist — holdout eval, baseline comparison, leakage scan, failure mode documentation.
not rated 1 yesterday A 20 tokens
original MIT
experiment
09Command Claude Code
Scaffold a new tracked experiment — create notebook, set up tracking, log baseline, define success criteria.
not rated 1 yesterday A 21 tokens
original MIT
plan
10Command Claude Code
Produce a short written plan before implementing anything nontrivial, so the approach is explicit before code starts — and get human approval before any state-changing apply.
not rated 1 yesterday A 31 tokens
original MIT
verify
11Command Claude Code
The standard pre-merge verification checklist for infrastructure changes — plan/validate/lint/policy checks, tests, security pass, rollback path, and documentation, all confirmed before a change is considered done.
not rated 1 yesterday A 40 tokens
original MIT
ship
12Command Claude Code
Quick pre-ship checklist to run before pushing or merging a change.
not rated 1 yesterday A 14 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: