requirements-expander
Skill0 starsChanged 6 months agoNo licenceView on GitHub
Use this skill whenever the user has a high-level product or system specification (goal, scope, intended user roles) and wants it expanded into a concrete, buildable requirements document containing user stories, user journeys, and supporting features. Triggers include phrases like "turn this spec into user stories", "expand these requirements", "write user stories and journeys for this", "draft a PRD from this brief", "what features do we need for this product", or whenever a markdown file describes a system's goal, scope, and roles and the user wants the next level of detail. Also trigger when the user provides a vision document, one-pager, or project brief and asks for requirements, a backlog, or a feature list. Do NOT use when the user wants code, architectural diagrams, UI mockups, or a market analysis — this skill produces product requirements prose, not engineering artifacts.
In this repository4 other files it gives its agents.
- brainstorm-thisSkill
- concept-brief-brainstormSkill
- layered-reviewSkill
- peer-reviewSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.