review-flow: Skill for Claude Code

Discovery - Business Exploration

Persona

Read .claude/roles/specifier.md — adopt this profile and follow all its rules.

Philosophy

Discovery comes BEFORE specs. We explore:

• The problem — not the solution
• The users — their pain points, not their requests
• The value — the benefit, not the feature

"Fall in love with the problem, not the solution." — Uri Levine

---

Activation

This skill activates when the user wants to explore:

• "I want to explore...", "What problem are we solving?"
• "Who are the users?", "Discovery on..."
• "What is the value proposition?"
• "Lean canvas for...", "Persona of..."

---

Produced artifacts

Artifact	File	When to use
Problem Statement	docs/business/problems/<name>.md	Define the problem precisely
Persona	docs/business/personas/<name>.md	Understand who has the problem
Lean Canvas	docs/business/canvas/<name>.md	Overview of an opportunity

---

Workflow

Entry point

DISCOVERY - Start

You want to explore: [subject]

Where do we begin?
1. Problem Statement — What problem exactly?
2. Persona — Who has this problem?
3. Lean Canvas — Overview of the opportunity?

Choose your entry point, or tell me what you already know.

---

Problem Statement

Construction dialogue

PROBLEM STATEMENT - Exploration

I see: [vague description of the problem]

Let's dig deeper:
1. Who exactly has this problem?
2. When/where does it manifest?
3. What do they do today to work around it?
4. What is the consequence if we don't solve it?

Answer what resonates, we'll iterate.

Output template

File: docs/business/problems/<name>.md

# Problem Statement: [Explicit title]

## The problem

[Persona] encounters [problem] when [context/trigger].

Today, [persona] [current behavior / workaround].

This causes [negative consequence] and [measurable impact].

## Frequency and severity

| Dimension | Assessment |
|-----------|------------|
| Frequency | [daily/weekly/monthly/occasional] |
| Severity | [blocking/hindering/irritating] |
| Affected population | [estimate] |

## Hypotheses to validate

- [ ] [Hypothesis about the existence of the problem]
- [ ] [Hypothesis about frequency]
- [ ] [Hypothesis about impact]

## What the problem is NOT

- [Red herring 1 — why it's a red herring]
- [Red herring 2]

## Research questions

- [Open question to explore]