From sdd-flow
Turn a rough task or idea into a decision-closed, senior-reviewable requirement by asking structured questions grounded in the existing codebase. Only draft the final artifact after all key decisions are resolved and the user confirms.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdd-flow:enrich-user-storyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help the user transform a vague task or idea into a **decision-closed, technically clear requirement**.
Help the user transform a vague task or idea into a decision-closed, technically clear requirement.
This artifact must be understandable by a senior engineer and serve as input for Spec-Driven Development (SDD) planning.
Do not optimize for wording.
Optimize for clarity, completeness, and closed decisions.
You MUST read the following file before asking any questions:
SDD/docs/doc_architecture.md
If you cannot access or read this file, stop and inform the user.
Read the input and briefly identify:
Ask questions in the same language used by the user.
Your goal is NOT to explore — it is to force decisions.
Rules:
Your questions MUST collectively cover these dimensions:
Solution shape
(e.g. new endpoint vs extending existing behavior)
Expected output
(what must be returned and in what form)
Behavior
(normal flow, edge cases, and failure scenarios)
Actor and usage context
(who uses this and why)
Scope boundaries
(what is in scope vs out of scope)
Success criteria
(how we know this is correctly implemented)
If any of these is unclear, you MUST ask about it.
Before proposing any suggested default:
SDD/docs/doc_architecture.mdSuggested defaults must be grounded in:
Avoid generic suggestions if code-based evidence is available.
When suggesting defaults:
When all key decisions are resolved, ask:
"Everything looks clear now. Do you want me to draft the final requirement?"
Do not write it yet.
Only if the user explicitly confirms, write the final artifact.
Respond in the same language as the user:
Suggested default:
Suggested default:
Respond in the same language as the user:
All key decisions are clear and no relevant ambiguity remains.
Do you want me to draft the final requirement?
Respond in the same language as the user:
As a ,
I want ,
so that .
npx claudepluginhub bisalta/ai-forge --plugin sdd-flowProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.