Browse / Software development / sdd
sdd
genkovich
Spec-Driven Development for Claude Code: 12 atomic Socratic skills + a TDD implement engine (agent-team & dynamic-workflow modes)
Open genkovich/sdd → Does not match the four rules.
Built for agents
ships .agents and nothing for other agents.
In its own words
A self-contained Claude Code plugin that carries a feature from a one-line idea to reviewed, verified, shipped code through 22 atomic, stack-agnostic skills and a TDD implementation engine — with a living roadmap above the per-feature flow and a design pipeline (design-system · ux-flows · screens) for UI features.
Every skill is Socratic (it walks decisions with you, it doesn't dump a wall of output), gated (a stage hard-refuses when its prerequisite artifact is missing), and stack-agnostic (no language, tracker, or test tool is hard-coded — the skills detect what your repo uses). The Q&A skills (specify / clarify / design) are also depth-tunable — an easy / medium / hard dial decides how much the skill decides for you vs. interrogates you with trade-offs.
Requirements
SDD runs on any Claude plan / model tier — no skill requires a specific model:
- Skills declare
model: inheritand run on your session model — run your SDD session on the
strongest tier your account has.
- The judgment agents (reviewer / critic / devils-advocate / strategist / analyst) default
to opus. No Opus access? Set judgment_model: sonnet in .claude/sdd.local.md — the supported path. Fable access? The floor rule lifts judgment to your session model automatically, or pin judgment_model: fable explicitly.
- A model tier that turns out unavailable degrades, never blocks: the dispatch retries once on
Quoting 6% of the README. Read the rest on GitHub ↗
What came from it 1
Read from the repository's git tree on 2026-08-17.