Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From sdd
Guides users through a structured discovery interview to define project scope, then generates SDD idea documents and a first spec.md ready for approval from a plain-language description.
How this command is triggered — by the user, by Claude, or both
Slash command
/sdd:new project description in plain languagecommands/sdd/The summary Claude sees in its command listing — used to decide when to auto-load this command
Guide the user from zero to a first spec ready for approval. Respond in the user's language (EN/ES). Ask ONE short question at a time; no jargon. 1. If `$ARGUMENTS` is empty, ask for the project in plain language. Then run a short discovery interview — one question at a time, only what is missing: - Problem and main goal (who hurts today, what changes when this works?). - MVP scope: what is IN and what is explicitly OUT. - Constraints: deadline, budget, tech the user must/can't use, existing systems to respect. - Stack: only if the user has one in mind; otherwise propose later ...
Guide the user from zero to a first spec ready for approval. Respond in the user's language (EN/ES). Ask ONE short question at a time; no jargon.
$ARGUMENTS is empty, ask for the project in plain language. Then run a short discovery interview — one question at a time, only what is missing:
plan.md, not here../scripts/install-spec-sidecar.sh <path> --profile=recommended (SDD artifacts in ./spec/, code stays in the project root)../scripts/create-www-project.sh <name> <agent>.idea/IDEA_GENERAL.md (or ./spec/idea/IDEA_GENERAL.md) with name, problem, goal, MVP scope../scripts/new-spec.sh "<feature>" "<owner>" (sidecar: ./spec/scripts/new-spec.sh). Visual alternative: the SDD Builder can create and connect spec cards on a canvas (guide 51). / Alternativa visual: el SDD Builder crea y conecta tarjetas de spec en un lienzo (guía 51). Its ✨ assistant drafts the whole board (idea → epics → specs) from one sentence. / Su asistente ✨ genera el board completo (idea → épicas → specs) desde una frase.spec.md with the user: user story, Given/When/Then scenarios, EARS acceptance criteria (WHEN [trigger], THE SYSTEM SHALL [behavior]), out of scope./sdd:gate as the next step.Hard stop: do NOT write project code in this command. Base creation needs no consent; implementation later will.
npx claudepluginhub juanklagos/spec-driven-development-template --plugin sdd/specGuides the user through clarifying questions and generates a structured specification document (SPEC.md) covering objective, features, tech stack, boundaries, and more.
/sdd-helpTeaches the Spec-Driven Development methodology, explains concepts and the change lifecycle, and guides users in discovering what capabilities are available.
/buidl-specRefines a raw idea through challenge interrogation (five gates, questions, pre-mortem) into three spec documents: requirements.md, design.md, tasks.md, saved to .claude/loop/sessions/<name>/spec/ for later /buidl.
/specifyTransforms project briefs into structured specifications with functional requirements, acceptance criteria, and testable requirements. Supports --input and --feature flags.
/interview-specGenerates comprehensive specification documents through deep iterative interviews with proactive research and optional subagent-based exploration.
/project-descriptionInterviews the developer to sharpen a project idea, discover the tech stack, and produce a structured project description at .spec/init/project-description.md.