specddlisted

Spec-driven development orchestrator that turns vague, top-of-mind feature requests into production-grade specifications before any code is written. ALWAYS use this skill whenever the user describes a feature, change, capability, screen, flow, or new component in plain language — even if they don't explicitly ask for a spec. Triggers on phrases like "build me", "make me", "add a feature", "I want to", "help me create", "implement", "let's build", "I need a", "can you make", "create a screen/page/component", or any new-feature request that lacks complete requirements (missing user stories, acceptance criteria, edge cases, error/empty/loading states, accessibility, or non-functional requirements). Interviews the user to fill gaps, applies UX/UI common sense, produces a structured spec + plan + tasks, then implements against the spec. Use this BEFORE writing any code for non-trivial features. Skip only for true one-liners (rename a variable, fix a typo, answer a research question) or work that is purely investig
mnyok9939/specdd · ★ 1 · AI & Automation · score 74

Install: claude install-skill mnyok9939/specdd

# specdd — Spec-Driven Development ## What this skill does User requests for features are incomplete by design — the user gives you the top-of-mind 30%, not the full spec. Coding from that ships things that compile but miss the actual intent, skip the boring-but-critical states (loading, empty, error, edge), and feel unpolished. specdd inverts that: you produce a spec the user agrees with **before** writing code. The spec captures intent, the user, the UX, edge cases, and non-functional requirements. The user keeps creative control; you stop guessing. Not waterfall. The spec is small, agent-readable, revisable. Goal is alignment, not bureaucracy. ## When to use Use it for any feature, screen, flow, component, API, change, or capability — even a one-line request. Skip for: one-liners (rename, typo), pure Q&A or research, bugs with clear repro, or continuing in-progress work that already has a spec. If unsure, use it. Under-use is the more common mistake. ## Scale ceremony to scope | Scope | Signal | Artifacts | |---|---|---| | **Quick** | Single component, <30 min, no new surface area | Inline mini-spec (5–8 bullets) in chat. No files. | | **Feature** | New UI / flow, 1–4 hours | `spec.md` + `plan.md` inline or as files. Skip tasks. | | **Project** | Multi-day, multiple files/services | `spec.md` + `plan.md` + `tasks.md` as files in `specs/<feature-name>/`. | User can override: "just a quick one" or "do this properly". ## The workflow ``` 1. TRIAGE → scope, s