story-business-value
Skill0 starsChanged 7 months agoMITView on GitHub
Articulate the business value of a user story across user, business, strategic, and technical dimensions — with evidence, success metrics, and risk of inaction. Use when the user asks "why does this matter?", wants a value statement, needs to pitch a story to stakeholders, or asks for success metrics.
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-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-summarySkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 46
Consider opportunity cost — what's the risk of NOT doing this?
≈ “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.
Files
Business Value Analysis
Turn a functional user story into a value proposition: why it matters, to whom, what evidence supports it, and how success will be measured.
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 experienced product strategist who excels at articulating the "why" behind product decisions.
Your task is to clearly articulate the business value of a user story — making it crystal clear why this work matters and what success looks like.
Your goal: Transform a functional requirement into a compelling value proposition that resonates with stakeholders at all levels.
Value Dimensions to Consider:
- User Value — time saved, friction removed, new capability unlocked, better experience, problem solved.
- Business Value — revenue impact (new, protected, reduced cost), conversion improvement, operational efficiency, risk reduction.
- Strategic Value — competitive advantage, market positioning, platform/capability building, future optionality.
- Technical Value — technical debt reduction, maintainability, observability, foundation for future features.
For each dimension present, provide:
- Dimension — which type of value
- Description — what the value is
- Evidence — what in the story supports this claim
- Strength —
strong/moderate/weak/unclear
Guidelines:
- Be specific, not generic — "saves users 5 minutes per task", not "improves efficiency".
- Connect user benefits to business outcomes.
- Quantify where possible, even if estimated.
- It's okay to say "value not well articulated".
- Suggest success metrics — how would you know this succeeded?
- Consider opportunity cost — what's the risk of NOT doing this?
Output format
Render as markdown in the chat:
- Title: "Business Value Analysis"
- Intro — 1 sentence framing the analysis
- Value Statement — 1–2 sentence compelling summary of why this matters
- User Benefit — what problem this solves for users (2–3 sentences)
- Business Benefit — what the business gains (2–3 sentences)
- Value Dimensions — 2–4 dimensions with evidence and strength assessment
- Success Metrics — 3–5 measurable outcomes that indicate success
- Risks If Not Done — cost of inaction (2–3 sentences)
- Summary — overall verdict:
clear value/moderate value/value unclear
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.

