Contract
- Input: product idea, user feedback, business problem, stakeholder input.
- Output: PRD with problem, goals, user stories, acceptance criteria, metrics, timeline.
- Side effects: none (design only; does not build product).
- Dependencies: stakeholder input (optional).
- Stop condition: PRD saved; metrics and timeline defined.
- Risk: low.
- Boundary: writes PRD; does not make product decisions unilaterally.
Product Requirements Document
Turn a product idea into a structured PRD with aligned goals, measurable outcomes, and clear scope.
Process
1. Problem statement
- What problem does this solve for users?
- Who is affected? (user segment)
- How is it solved today? (workaround, competitor, manual process)
- What is the cost of not solving?
Completion criterion: problem clear; user segment defined.
2. Goals
- Business goal: revenue, retention, efficiency, market position.
- User goal: task completed faster / easier / with less error.
- Technical goal: system reliability, performance, maintainability.
- Measurable: each goal has a metric and target.
Completion criterion: goals with metrics saved.
3. User stories
For each user journey: "As a [user type], I want [action] so that [benefit]."
- Acceptance criteria per story: given / when / then; conditions for pass.
- Priority: must-have / should-have / nice-to-have.
Completion criterion: stories with acceptance criteria saved.
4. Success metrics
- Leading (predictive): feature adoption rate, time-to-first-value, error rate.
- Lagging (outcome): revenue impact, retention, NPS, customer satisfaction.
- Dashboard: how will metrics be tracked (analytics tool, telemetry, survey)?
Completion criterion: metrics table saved.
5. Constraints and risks
- Technical: dependencies, performance, security.
- Regulatory: compliance (GDPR, accessibility, financial regulations).
- Timeline: dependencies, holidays, team availability.
- Risk mitigation per item.
Completion criterion: risks with mitigation saved.
6. Timeline and milestone
- Milestones with dates and deliverables.
- Dependencies between milestones.
- Review points (design review, user testing, release readiness).
Completion criterion: timeline saved with milestones.
1---2name: prod-prd-writing3description: Write Product Requirement Documents (PRDs) — problem statement, goals, user stories, acceptance criteria, success metrics, timeline — with stakeholder alignment.4---56## Contract78- **Input:** product idea, user feedback, business problem, stakeholder input.9- **Output:** PRD with problem, goals, user stories, acceptance criteria, metrics, timeline.10- **Side effects:** none (design only; does not build product).11- **Dependencies:** stakeholder input (optional).12- **Stop condition:** PRD saved; metrics and timeline defined.13- **Risk:** low.14- **Boundary:** writes PRD; does not make product decisions unilaterally.1516# Product Requirements Document1718Turn a **product idea** into a structured PRD with aligned goals, measurable outcomes, and clear scope.1920## Process2122### 1. Problem statement23- What problem does this solve for users?24- Who is affected? (user segment)25- How is it solved today? (workaround, competitor, manual process)26- What is the cost of not solving?2728**Completion criterion:** problem clear; user segment defined.2930### 2. Goals31- **Business goal:** revenue, retention, efficiency, market position.32- **User goal:** task completed faster / easier / with less error.33- **Technical goal:** system reliability, performance, maintainability.34- **Measurable:** each goal has a metric and target.3536**Completion criterion:** goals with metrics saved.3738### 3. User stories39For each user journey: "As a [user type], I want [action] so that [benefit]."40- Acceptance criteria per story: given / when / then; conditions for pass.41- Priority: must-have / should-have / nice-to-have.4243**Completion criterion:** stories with acceptance criteria saved.4445### 4. Success metrics46- **Leading** (predictive): feature adoption rate, time-to-first-value, error rate.47- **Lagging** (outcome): revenue impact, retention, NPS, customer satisfaction.48- **Dashboard:** how will metrics be tracked (analytics tool, telemetry, survey)?4950**Completion criterion:** metrics table saved.5152### 5. Constraints and risks53- Technical: dependencies, performance, security.54- Regulatory: compliance (GDPR, accessibility, financial regulations).55- Timeline: dependencies, holidays, team availability.56- Risk mitigation per item.5758**Completion criterion:** risks with mitigation saved.5960### 6. Timeline and milestone61- Milestones with dates and deliverables.62- Dependencies between milestones.63- Review points (design review, user testing, release readiness).6465**Completion criterion:** timeline saved with milestones.
quantumquirkxyz