# Product Requirements (One-Page)

**Product / Feature:** [Name]

**Owner:** [Name / Team]   •   **Status:** [Draft / Active / Done]   •   **Last updated:** [YYYY-MM-DD]

---

## 1) Elevator Pitch
One-sentence description of the product/feature and the primary user benefit.

## 2) Problem / Opportunity
- Short bullet(s) describing the pain or opportunity this addresses.
- Who is impacted and why it matters now.

## 3) Goals & Success Metrics
- Primary goal: [short statement]
- Success metrics (KPI):
  - Metric 1 — target
  - Metric 2 — target

## 4) Key Users / Personas
- Persona A: primary tasks, technical level.
- Persona B: primary tasks, technical level.

## 5) Scope — Key Capabilities (MVP)
1. Capability 1 — acceptance criteria (one line)
2. Capability 2 — acceptance criteria
3. Capability 3 — acceptance criteria

## 6) Non-Functional / Constraints
- Performance: [e.g., startup < 100ms]
- Security: [e.g., OAuth2, TLS]
- Platforms: [macOS, Linux, Windows]

## 7) Timeline (high level)
- Phase 0.1: [scope] — [date]
- Phase 0.2: [scope] — [date]
- GA / 1.0: [date]

## 8) Risks & Open Questions
- Risk A → mitigation
- Open question 1 (decide by [date])

## 9) Acceptance & Rollout
- Who signs off: [roles]
- Rollout plan: [canary / beta / GA], rollback criteria

## 10) Contacts & Links
- Product lead: [name, email]
- Eng lead: [name, email]
- Spec / design / docs: [link(s)]

---

(Keep this one page; expand in a full PRD or tech spec as needed.)
_Copyright (c) 2026 The University of Texas at Austin and B-Tree Labs. Apache-2.0 licensed._
