requirements-to-spec
Skill1 starsChanged 5 months agoMITView on GitHub
Invoke when user describes product idea, feature request, or business need vaguely. "I want to build", "users need to be able to", "we need a", "product idea", "feature request", "spec this out". SDLC categories: Requirement Engineering (9 benchmarks).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 05-deepak-patidar/claude-skillstheir own version, first seen Jul 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 05-deepak-patidar/claude-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- apex-archSkill
- apex-debugSkill
- apex-flexSkill
- apex-infraSkill
- apex-novaSkill
- apex-perfSkill
- apex-reedSkill
- apex-reviewSkill
- apex-secSkill
- apexSkill
- apex-uiSkill
- bug-patchSkill
- debug-protocolSkill
- deploy-pipelineSkill
- full-stack-scaffoldSkill
- mvp-cutSkill
- perf-auditSkill
- pr-reviewSkill
- refactorSkill
- researchSkill
- sec-reviewSkill
- system-designSkill
- test-harnessSkill
- ui-generateSkill
The file
Files
Requirements to Spec Protocol
- EXTRACT user stories from description Format: As a [user type], I want to [action] so that [value]
- IDENTIFY acceptance criteria per story (Given/When/Then)
- CLASSIFY — Functional vs non-functional requirements
- FLAG ambiguities — list every unclear requirement with a specific question
- SCOPE — What's in MVP vs future?
- OUTPUT — Complete structured spec in markdown, ready for engineering
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.