# Product Brief — [PROJECT_TITLE]

**Created:** [DATE] via `/gsd:discover-product`
**Scope:** Product definition (what/why) — feeds `PROJECT.md` and `/gsd:model-domain`. Outcome-framed so the domain and architecture stay open. **This brief is a hypothesis, not a verdict** — its open assumptions feed an ongoing discovery cadence (Torres), not a one-time gate.

## Outcome (not output)

[The customer behavior or business metric we want to change — not a feature. e.g., "Shippers get a priced, matched carrier in seconds instead of days."]

## Desired outcomes (measurable — Ulwick ODI)

State 2–3 as *direction + metric + object* so "is it working?" is answerable. If the population is heterogeneous, list per-segment — don't average them away.

| Desired outcome (direction + metric + object) | For which segment | Under-served? (importance × dissatisfaction) |
|---|---|---|
| [e.g., "minimize the time to reconcile an invoice"] | [segment] | [high / unknown] |

## Target user & job

- **Specific user:** [the actual human/role for whom this is most acute/frequent/expensive]
- **Job (solution-free):** [verb + object, e.g., "book freight capacity for a load"]
- **Job story:** When [situation], I want to [motivation], so I can [outcome].

## Demand evidence (not interest)

| Signal | Evidence | Strength |
|--------|----------|----------|
| Current workaround | [what they do today + its cost in time/money] | strong / weak |
| Behavioral / money | [pre-pay, LOI, pilot, converted signups, "calls when it breaks"] | strong / weak |

[If evidence is all "interest" (waitlists, "sounds useful"), flag it — demand is unproven.]

## The wedge

[The narrowest version that fully solves one opportunity for one user this week. Which opportunity moves the outcome most, and why. Confirm: more than one solution is imaginable (else re-frame).]

## Four risks (status)

| Risk | Status | Evidence / cheapest test before building |
|------|--------|------------------------------------------|
| Value (will they choose it over the status quo?) | validated / open | |
| Usability (can they figure it out?) | validated / open | |
| Feasibility (can we build it — riskiest unknown?) | validated / open | |
| Viability (pricing/legal/sales/brand?) | validated / open | |

## Scope

- **Thin first slice (walking skeleton):** [the smallest end-to-end path]
- **Prioritized candidates (RICE):** [feature — R×I×C/E; or "deferred to discovery, value unproven"]
- **NOT in scope (deferred, one-line rationale each):** [...]

## Success

- **Outcome metric + by when:** [the behavior/metric change and the date]
- **PMF check:** [what would make ≥40% of core users "very disappointed" to lose this]

## Handoff notes

- **For `model-domain`:** [the job + journey steps and the key domain nouns/events to model]

## Assumptions to re-test (leap-of-faith)

The brief is a hypothesis. List the assumptions that must hold for the wedge to work, riskiest first, each with the cheapest next test — revisit after a handful of customer conversations (continuous discovery, not a gate).

| Leap-of-faith assumption | Riskiest? | Cheapest next test |
|---|---|---|
| [what must be true] | [yes / no] | [the test] |

---
*Product brief. Next: `/gsd:new-project` (if not done) → `/gsd:model-domain` → `/gsd:recommend-architecture`.*
