droam_sdd

Spec-Driven Development for Claude Code: 18 atomic, stack-agnostic skills + 10 subagents that carry a feature from idea → spec → design → data-model → API → tasks → tests → implement → review → ship → document, plus a `fix` express lane for small changes (it skips the backbone but keeps the test + independent review + doc-sync, gated on size — it refuses anything M+ and routes to the backbone), a TDD implementation engine, a living roadmap above the per-feature flow, and a living-documentation layer — the `document` skill + `doc-writer` subagent keep the repo's durable `docs/` true to what actually shipped. Start with `survey` (maps an existing codebase or bootstraps an empty one), walk the gated backbone — each stage reads the previous artifact and hard-refuses if missing — and keep `docs/roadmap.md` (Now/Next/Later, outcome-altitude, never dates) in sync as `specify` promotes a feature to Now and `ship` moves it to Shipped. The Q&A skills are depth-tunable (easy/medium/hard — decide-for-me vs. interrogate-me-with-trade-offs); the ideation analyses run as named subagents (researcher/strategist/analyst/devil's-advocate) gated by that dial; diagrams are presented in prose and written to file (never raw Mermaid dumped to the terminal); and every acceptance criterion is covered end-to-end. design is surface-aware: it declares the feature's target surfaces at the architecture stage (backend-service / web-frontend / mobile-app / desktop-app / cli / worker / library-sdk, each a C4 container) and downstream stages gate their output by that choice — the `ui` task layer, UI-driven sequence flows, and the component / visual-regression / e2e-through-UI frontend test tiers; `ui` work reuses the repo's existing design system (components / tokens / styling) from the architecture map, never reinvents. Every stage ends with a copy-ready handoff block — what changed, the files to review, then `/clear` + the next `/sdd:…` command.