product-requirements

name	product-requirements
description	Turn a product problem into scoped requirements, user outcomes, constraints, acceptance criteria, exclusions, and decision-ready tradeoffs.

Product Requirements

Use when a product idea or request needs enough definition for design and engineering to act without guessing the product intent.

Procedure

1. Define the user/customer problem, target audience, and evidence that it matters.
2. State the desired outcome in observable behavior or business terms.
3. Capture constraints and dependencies that shape the solution space without prematurely prescribing implementation.
4. Define in-scope behavior, important states/edge cases, and explicit non-goals.
5. Write acceptance criteria around user-visible or system-observable outcomes.
6. Surface unresolved product decisions and make tradeoffs explicit.
7. Confirm the scope is the smallest coherent version that achieves the intended outcome.

Quality gate

Design and engineering should understand what success means while retaining appropriate freedom over how to achieve it.