# Story Business Value

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

- Skill: `jdinkla/story-business-value` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jdinkla/story-business-value`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jdinkla/story-business-value/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jdinkla (https://skillmd.com/u/jdinkla)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jdinkla/story-business-value

---


# 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:

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 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:**

1. **User Value** — time saved, friction removed, new capability unlocked, better experience, problem solved.
2. **Business Value** — revenue impact (new, protected, reduced cost), conversion improvement, operational efficiency, risk reduction.
3. **Strategic Value** — competitive advantage, market positioning, platform/capability building, future optionality.
4. **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:**
1. Be specific, not generic — "saves users 5 minutes per task", not "improves efficiency".
2. Connect user benefits to business outcomes.
3. Quantify where possible, even if estimated.
4. It's okay to say "value not well articulated".
5. Suggest success metrics — how would you know this succeeded?
6. 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.