blackpeanut/awesome-sdd

v1.1.0MIT

Awesome SDD, maintained by blackPeanut. Spec-Driven Development pipeline: 24 atomic Socratic skills (survey/scaffold → spec → ux-flows → design → data-model → api → screens → tasks → tests → implement → review → ship) + a living decomposition roadmap (steps + dependency graph + parallel-safe execution waves) above the per-feature flow, plus a TDD implementation engine. Depth-tunable Q&A (easy/medium/hard), surface-aware design (backend/web/mobile/desktop/CLI/worker/library as C4 containers), a design pipeline for UI features (design-system canon / ux-flows / per-state screens manifest — auto-skipped for backend-only work), every acceptance criterion covered end-to-end, and a copy-ready handoff block at every stage. Skills are the open Agent Skills format (SKILL.md); the Claude-specific mechanisms degrade per skills/_shared/tool-adapters.md.

GitHub Open Website

skills

clarify

Use to run an ambiguity sweep over a written spec.md and close every under-specified point before planning or design proceeds — so two engineers can't reasonably build different things from the same spec. Triggers on "clarify {slug}", "find ambiguities in {slug}", "is the spec ready", "sharpen the spec", "/awesome-sdd:clarify {slug}". Re-reads the spec, dispatches a clean-context devil's-advocate subagent to list where the spec forks, then for each ambiguity runs AskUserQuestion to RESOLVE it (tighten §1/§5/§6 in place) or DEFER it (→ §8 Open questions with owner+due). Output: an updated docs/features/{slug}/spec.md with every ambiguity resolved or deferred — none dangling. Hard-refuse if spec.md is missing.

Read SKILL.md at the source

Pinned to revision 8be88261fac7, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.