user-stories
Skill0 starsChanged 4 months agoMITView on GitHub
Use when writing, reviewing, splitting, or refining user stories and acceptance criteria for a product backlog. Owns story + AC quality — the INVEST gate, the per-AC testability linter, and the structured story-spec contract. Touches no filesystem or external system; the caller owns all orchestration.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- travissmithv1/claude-skillstheir own version, first seen Nov 16, 2026
- Stijnus/dsh-rev-engtheir own version, first seen Nov 8, 2026
- daveebbelaar/bawatheir own version, first seen Nov 8, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- shangyiy/life-kittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use brainstorm-experiments-new, brainstorm-experiments-existing and 10 more.
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.
skytiger6724Skillbrainstorm-experiments-new
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Also in 9 projects that use this
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 7 projects that use this
45ckSkillpestle-analysis
Also in 7 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 7 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 10 projects that use this
About-IntelligenceSkillproduct-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 7 projects that use this
- +6 more from skytiger6724
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- daveebbelaar/bama★ 1.7ksame name
- Mehdibargach/claude-code-pm-skills★ 97same name
- daveebbelaar/bawa★ 17same name
- shangyiy/life-kit★ 10same name
- felipereisdev/user-stories-skill★ 9same name
- robconery/kolea★ 7same name
- The-Utopia-Studio/skills★ 6same name
- gabriellst/codm★ 4same name
- JailtonJunior94/skills★ 4same name
- Adhamxon/claude-code-skills★ 2same name
15 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 repository8 other files it gives its agents.
- checkpointSkill
- design-themeSkill
- dispatch-agentsSkill
- githubSkill
- github-templatesSkill
- gitSkill
- productSkill
- technical-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Every story satisfies all six (first three checked during drafting, last three during validation):
- Distinctive: line 74
Run on every AC; each must pass all four:
- Very specific: line 83
Rewrite: when the requirement is clear but the wording weak.
- Distinctive: line 84
Escalate: when the requirement itself is unclear (missing trigger, ambiguous outcome, unknown threshold) — re-open Discovery.
- Distinctive: line 92
Every Discovery capability covered by ≥1 story's ACs.
- Distinctive: line 94
No implementation details as AC outcomes.
- Distinctive: line 95
No foundational work as stories.
- Very specific: line 96
Every cross-story dependency explicit in depends_on_titles.
- Distinctive: line 97
No gold-plating — every AC traces to stated intent or a surfaced edge case.
- Distinctive: line 112
Never invent scope — run Discovery.
- Distinctive: line 113
Never add technical details to ACs.
- Distinctive: line 114
Never silently rewrite an AC whose underlying requirement is unclear — escalate.
- Distinctive: line 115
Never touch GitHub, filesystem, or external systems.
“Common” is measured: kept by at least 6 in 10 of the 24 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 Expertise
Discovery → draft via the Story Spec → Testability Linter on every AC → Validation → Ordering → emit per Notes Rendering.
Discovery Protocol
Synthesise understanding across the six categories; any gap that would change scope is blocking. Probe each:
- Role — who specifically, with context (not "user").
- Intent — the outcome in user terms, not implementation.
- Value — why it matters; if only statable as tautology, not ready.
- Definition of done — the observable success condition.
- Constraints — platform, compliance, performance, permissions, flows to preserve.
- Edge and failure cases — invalid input, missing permission, network failure, missing data, repeated action.
Present synthesis → ask every blocking gap via AskUserQuestion (max 4 per call; batch if more) — concrete options per question, never open-ended prose; don't draft yet. Re-synthesise per response until no blocking gaps remain → confirm in one line before output. Non-blocking ambiguities → resolve with a stated assumption.
Scope Boundary
User stories capture user-observable behaviour only. Out of scope as stories: design tokens, primitives, shared components, schemas, migrations, data models, infrastructure, cross-cutting modules, refactors, spikes.
Foundational work needed -> never smuggle it in or invent a "technical story":
- Team prerequisite → separate task/spike (outside this skill); add to
depends_on_titlesonly if it blocks the user-observable outcome. - User asked for technical breakdown → stop; say this skill produces user stories only; offer to list technical work as plain items.
Story Spec
Draft each story to this spec — Scope Boundary governs what becomes a story, INVEST (first three) and AC Format govern content, Splitting when too big:
- title: "[Story] <title>"
user_story: "As a <role>, I want <action> so that <benefit>"
acceptance_criteria:
- "<AC>"
notes:
edge_cases: ["<text>", ...]
design_instructions: [{label: "<filename.md>", url: "<url>"}, ...]
mockups: [{label: "<filename.html>", url: "<url>"}, ...]
references: [{label: "<text>", url: "<url>"}, ...]
depends_on_titles: ["<title>", ...]INVEST
Every story satisfies all six (first three checked during drafting, last three during validation):
- Independent — deliverable without another story first; unavoidable dependencies go in
depends_on_titles. - Negotiable — the "what" is fixed, the "how" open; no implementation in the want clause.
- Valuable — observable value to a user or stakeholder; a tautological "so that" means re-run Discovery on intent.
- Estimable — scope clear enough to ballpark; fails on vague scope, unknown dependencies, hidden research.
- Small — completable within a sprint by one team (see Splitting).
- Testable — every AC passes the linter.
AC Format
When X, then Y.orGiven X, when Y, then Z.- Checklist bullets when the story is about completeness, not behaviour. Don't force Given/When/Then where it doesn't fit.
- An AC may cite a reference by label instead of restating detail.
- Target 2–5 ACs; fewer suggests under-specification, more suggests splitting.
Splitting
Story failing Small or with >~5 ACs splits. Techniques, preference order: workflow steps → happy path vs alternates → CRUD operations → data/input variation → interface surface. Never split by technical layer (frontend/backend story) — violates Independent + Valuable.
Testability Linter
Run on every AC; each must pass all four:
- Observable — verifiable without reading code or internal state.
- Located — names the user-visible area/screen/surface.
- Specific — concrete trigger and outcome, not "works correctly".
- Verifiable — a non-engineer can confirm pass/fail in a running system.
On failure choose one:
- Rewrite when the requirement is clear but the wording weak. Preserve meaning; record
{original, rewritten, reason}, aggregate asrewrote_for_testability. - Escalate when the requirement itself is unclear (missing trigger, ambiguous outcome, unknown threshold) — re-open Discovery; never silently rewrite.
Cap: more than three rewrites for one story → stop and escalate the whole story.
Validation
Across the full set:
- Every Discovery capability covered by ≥1 story's ACs.
- No duplicate scope.
- No implementation details as AC outcomes.
- No foundational work as stories.
- Every cross-story dependency explicit in
depends_on_titles. - No gold-plating — every AC traces to stated intent or a surfaced edge case.
Ordering
Dependency depth first (no depends_on_titles first), then user value within each depth level.
Notes Rendering
design_instructions—- Design Instructions: [label](url). Multiple → nested list.mockups— same pattern under- Mock UI:.edge_cases— one bullet per item.depends_on_titles—- Depends on: <resolved refs>.
Constraints
- Never invent scope — run Discovery.
- Never add technical details to ACs.
- Never silently rewrite an AC whose underlying requirement is unclear — escalate.
- Never touch GitHub, filesystem, or external systems.
- AC reshape: only
## Acceptance Criteriaand## Notesmay change.
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.

