user-story
Skill0 starsChanged 2 months agoMITView on GitHub
Write role-based user stories from an agreed product definition.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- callmeradical/skillstheir own version, first seen Nov 1, 2026
- SecuringTheRealm/str-mcp-purviewtheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- mhylle/claude-skills-collection★ 20same name
- ulises-jeremias/agent-toolkit★ 19same name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- The-Utopia-Studio/skills★ 6same name
- razbakov/skills★ 4same name
- SecuringTheRealm/str-mcp-purview★ 4same name
- CrazyElephantX/OpenCode★ 2same name
- agrivisionai/claude-skills★ 1same name
- craigspaterson/agent-skills★ 1same name
9 more not listed
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use when the task matches: user-story, user stories, as a user.
- Distinctive: line 24
Write stories as role + need + outcome.
- Distinctive: line 25
Keep one primary outcome per story.
- Distinctive: line 38
Keep Product validation and engineering verification distinct.
- Distinctive: line 39
Do not claim completion without evidence.
- Distinctive: line 43
Do not encode architecture choices inside stories.
- Distinctive: line 44
Do not invent personas without Product agreement.
- Distinctive: line 45
Do not skip acceptance-criteria linkage.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
user-story
When to use
Use when the task matches: user-story, user stories, as a user.
Purpose
Break product intent into stories Development and AI can implement.
Inputs
- Feature brief
- Users in scope
- Business rules
Process
- Write stories as role + need + outcome.
- Keep one primary outcome per story.
- Mark priority and dependencies between stories.
- Exclude technical tasks disguised as stories.
Outputs
- User stories
- Story priority notes
- Out-of-scope story list
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not encode architecture choices inside stories.
- Do not invent personas without Product agreement.
- Do not skip acceptance-criteria linkage.
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.