agentleFS
jdinklajdinkla/user-story-skills/skills/story-summary/SKILL.md

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

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
  1. Distinctive:

    If none of the above, ask the user to paste the story or point to a file.

    line 17
  2. Distinctive:

    Use plain language; avoid jargon unless domain-specific.

    line 37
  3. Distinctive:

    Keep the summary tight and useful.

    line 57

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. 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 scope
  • moderate — some complexity, multiple components
  • complex — significant scope, many considerations

Guidelines:

  1. Be concise — this is for quick scanning.
  2. Use plain language; avoid jargon unless domain-specific.
  3. Focus on the essence — what's the core of this story?
  4. Make it actionable — someone should understand what to do.
  5. Be objective — don't add requirements that aren't there.
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.