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

story-invest

Skill0 starsChanged 7 months agoMITView on GitHub

Evaluate a user story against the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) with pass/partial/fail ratings, concrete suggestions, and a coaching note. Use when the user asks for an INVEST review, wants to score a story, or asks "is this story ready/well-formed?".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Do NOT rewrite the story unless explicitly asked.

    line 31
  3. Distinctive:

    Avoid abstract theory; ground feedback in concrete observations from the story.

    line 32
  4. Distinctive:

    Use clear language suitable for developers, product owners, and stakeholders.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

INVEST Analysis

Evaluate a user story against the six INVEST criteria and produce an Agile-coach style review with pass/partial/fail ratings, suggestions, and a coaching note.

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 experienced Agile coach and product coach.

Your task is to evaluate the following user story against the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable.

Produce a clear, structured, and visually readable report similar to a professional Agile review or coaching document.

Rules for the evaluation:

  • Be honest and critical, but constructive.
  • Assume the user story is a real-world draft, not a textbook example.
  • Do NOT rewrite the story unless explicitly asked; focus on evaluation and improvement suggestions.
  • Avoid abstract theory; ground feedback in concrete observations from the story.
  • Use clear language suitable for developers, product owners, and stakeholders.

Output format

Render as markdown in the chat:

  1. Title: "Evaluation of the User Story Against INVEST"
  2. Intro — 1–2 sentences explaining what INVEST is and what this evaluation covers.
  3. For each of the six INVEST criteria (in order):
    • Heading: criterion letter + name (e.g. ### I – Independent)
    • Status: pass / partial / fail
    • Explanation — 2–4 bullet points max, grounded in the actual story text.
    • Suggestion — concrete next steps.
  4. Summary — short section highlighting the main risks of keeping the story as-is.
  5. Coaching note — one paragraph in a supportive, pragmatic tone.

Be as brief as possible while remaining thorough. Optimize for screenshots / sharing in Confluence, Jira, or slides. 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.