sddp-specify
Skill98 starsChanged 27 days agoMITView on GitHub
Create a feature specification from a feature description. Direct command-bar dispatch only; do not select for general queries.
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-autopilotSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- sddp-initSkill
- sddp-planSkill
- sddp-prdSkill
- sddp-projectplanSkill
- sddp-qcSkill
- sddp-regenSkill
- sddp-reverseengineerSkill
- sddp-systemdesignSkill
- sddp-tasksSkill
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-autopilotSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- sddp-initSkill
- sddp-planSkill
- sddp-prdSkill
- sddp-projectplanSkill
- sddp-qcSkill
- sddp-regenSkill
- sddp-reverseengineerSkill
- sddp-specifySkill
- sddp-systemdesignSkill
- sddp-tasksSkill
- adr-authoringSkill
- artifact-conventionsSkill
- clarification-strategiesSkill
- compact-communicationSkill
- evidence-led-authoringSkill
- implementation-standardsSkill
- instructions-managementSkill
- markdown-compressionSkill
- plan-authoringSkill
- quality-assuranceSkill
- sdd-methodologySkill
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-autopilotSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If the user provided no message, set $ARGUMENTS to empty and let the skill handle it.
- Very specific: line 17
When the shared workflow requires user decisions and AUTOPILOT = false:
- Distinctive: line 18
Ask the user explicitly in chat and wait for the reply before continuing.
- Distinctive: line 21
Do not infer an answer from silence, partial output, or prior recommendations.
- Very specific: line 23
When AUTOPILOT = true, keep following the shared workflow's automatic decision rules unchanged.
- Distinctive: line 25
When the workflow says Delegate, read the exact referenced sub-agent file at that point, not before, then perform the delegated task …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Argument hint: [feature description]
Command category: feature-delivery
Prerequisites: project-instructions
You are starting a NEW specification workflow. Your sole purpose is to capture WHAT users need and WHY — requirements, user stories, and success criteria. Disregard any prior implementation context, code discussion, or task execution from this conversation. Do not write code, do not reference tasks, do not execute commands. Focus exclusively on the feature description and requirements.
Input
$ARGUMENTS = The user's message provided alongside this command invocation.
If the user provided no message, set $ARGUMENTS to empty and let the skill handle it.
Load and follow the workflow in .github/sddp/workflows/specify-feature/WORKFLOW.md.
When the shared workflow requires user decisions and AUTOPILOT = false:
- Ask the user explicitly in chat and wait for the reply before continuing.
- Present the recommended option as guidance only; do not choose it on the user's behalf.
- Allow free-form answers anywhere the shared workflow allows them.
- Do not infer an answer from silence, partial output, or prior recommendations.
When AUTOPILOT = true, keep following the shared workflow's automatic decision rules unchanged.
When the workflow says Delegate, read the exact referenced sub-agent file at that point, not before, then perform the delegated task yourself.
Report progress to the user at each major milestone — summarize what has been completed and what remains.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

