one-pager-prd

# One-Pager PRD

## Table of Contents
- [Purpose](#purpose)
- [When to Use](#when-to-use)
- [What Is It](#what-is-it)
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

## Purpose

Create concise, decision-ready product specifications that align stakeholders on problem, solution, users, success metrics, and constraints—enabling fast approval and reducing back-and-forth.

## When to Use

**Early-Stage Product Definition:**
- Proposing new feature or product
- Need stakeholder alignment before building
- Scoping initiative for resource allocation
- Pitching idea to leadership for approval

**Documentation Needs:**
- Capturing requirements for engineering handoff
- Documenting decisions for future reference
- Creating spec for cross-functional team (PM, design, eng)
- Recording what's in/out of scope

**Communication:**
- Getting buy-in from multiple stakeholders
- Explaining complex feature simply
- Aligning sales/marketing on upcoming releases
- Onboarding new team members to initiative

**When NOT to Use:**
- Detailed technical design docs (use ADRs instead)
- Comprehensive product strategy (too high-level for one-pager)
- User research synthesis (different format)
- Post-launch retrospectives (use postmortem skill)

## What Is It

A one-pager PRD is a 1-2 page product specification covering:

**Core Elements:**
1. **Problem:** What user pain are we solving? Why now?
2. **Solution:** What are we building? (High-level approach)
3. **Users:** Who benefits? Personas, segments, use cases
4. **Goals & Metrics:** How do we measure success?
5. **Scope:** What's in/out? Key user flows
6. **Constraints:** Technical, business, timeline limits
7. **Open Questions:** Unknowns to resolve

**Format:**
- **One-Pager:** 1 page, bullet points, for quick approval
- **PRD (Product Requirements Document):** 1-2 pages, more detail, for execution

**Example One-Pager:**

**Feature:** Bulk Edit for Data Tables