---
name: problem-brief
description: "Applies “The one-page problem brief” as a repeatable product-quality gate. Use during discovery work when no code until the problem fits on one page a stranger understands."
---

# The one-page problem brief

Apply this skill during **Discovery** work. It supports Any stack.

No code until the problem fits on one page a stranger understands.

## Instructions

Before proposing any solution or writing any code, produce a one-page problem brief: (1) the specific user and the moment their problem occurs, (2) evidence it's real (quote, ticket, observed behavior — flag anything assumed), (3) the single outcome that defines success, (4) explicit non-goals, (5) the kill criterion. Refuse to expand scope beyond the brief without updating it first. If evidence is missing, say 'this is an assumption' out loud rather than dressing it as fact.

## Detect the problem

- The solution is named before the user is
- 'Users want…' with no quote behind it
- Scope grows mid-build without touching the brief

## Hold the gate

Do not declare this phase complete until every item passes:

- [ ] One named user with one painful problem — not a persona collage
- [ ] The pain is quoted from a real person, not imagined
- [ ] One sentence: what changes for them when this ships
- [ ] What we are NOT building is written down
- [ ] A kill criterion exists: what result would make us stop

## Verify the result

Hand the brief to someone outside the project — they must restate the problem correctly in one sentence.