story-summary
Skill0 starsChanged 7 months agoMITView on GitHub
Generate a 30-second quick-reference summary of a user story — one-liner, what/who/why, key features, acceptance summary, complexity indicator, and tags. Use when the user wants a TL;DR, backlog-scanning summary, or handoff-ready synopsis of a story.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BAChapin/claude_skillstheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- BAChapin/claude_skills★ 0same 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 repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 37
Use plain language; avoid jargon unless domain-specific.
- Distinctive: line 57
Keep the summary tight and useful.
≈ “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
Story Summary
Distill a user story into a quick-reference synopsis that can be scanned in 30 seconds and used for documentation, handoff, or backlog overview.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an expert at distilling complex information into clear, concise summaries.
Your task is to create a quick-reference summary of a user story that can be scanned in 30 seconds and used for documentation, handoff, or backlog overview.
The summary answers:
- What is being built? (the feature/capability)
- Who benefits? (the user/persona)
- Why does it matter? (the value)
Complexity indicator:
straightforward— well-defined, limited scopemoderate— some complexity, multiple componentscomplex— significant scope, many considerations
Guidelines:
- Be concise — this is for quick scanning.
- Use plain language; avoid jargon unless domain-specific.
- Focus on the essence — what's the core of this story?
- Make it actionable — someone should understand what to do.
- Be objective — don't add requirements that aren't there.
- Preserve intent — capture the original meaning accurately.
Output format
Render as markdown in the chat:
- Title — story title or generated title if not present
- One-liner — single sentence capturing the essence (max 100 chars)
- What — 1–2 sentences describing what's being built
- Who — 1 sentence identifying the beneficiary
- Why — 1 sentence explaining the value/purpose
- Key Features — 3–5 bullet points of main features/capabilities
- Acceptance Summary — 1–2 sentences summarizing the acceptance criteria
- Complexity —
straightforward/moderate/complex - Tags — 3–5 suggested tags for categorization (e.g.
authentication,mobile,api,ux)
Keep the summary tight and useful. Less is more. No JSON.
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.

