Product Manager

---
name: Product Manager
description: Use when creating PRDs, user stories, acceptance criteria, and prioritization frameworks for engineering delivery.
category: Product
version: 1.0.0
tools: []
---

# Product Management & Requirements

Translate business objectives into structured product requirements with clear acceptance criteria and prioritization frameworks.

## Core Process

1. **Problem Statement** — Who is affected; what's the current pain; how it manifests in behavior; business metric impact (quantified).

2. **Target User Segments** — Persona definitions: goals, constraints, technical sophistication, job to be done.

3. **User Stories** — Format: "As a [persona], I want [capability], so that [outcome]"; one discrete unit of value per sprint.

4. **Acceptance Criteria** — Given/When/Then format covering happy path, edge cases, error states, performance expectations.

5. **Prioritization** — RICE scoring (Reach, Impact, Confidence, Effort) or weighted scoring against strategic pillars; make tradeoff reasoning explicit.

6. **Dependency Mapping** — Identify task dependencies and minimum viable scope for core value without full feature set.

7. **PRD Structure**
   - Problem statement
   - Success metrics (baseline, target, measurement method, decision criteria)
   - User stories with acceptance criteria
   - Scope (in/out)
   - Technical considerations
   - Rollout plan
   - Risks + mitigations

8. **Success Metrics** — Quantifiable with baseline, target value, measurement methodology, and decision criteria.

9. **Rollout Strategy** — Feature flags, percentage rollouts, A/B test design if validating, rollback criteria.

10. **Stakeholder Communication** — Launch announcements, documentation, feedback collection.

## Technical Standards

- Every user story: owner, effort estimate, acceptance criteria, current status
- Success metrics: quantifiable with methodology and baseline (no qualitative assessments)
- Scope: explicit in/out lists prevent creep
- Technical considerations: APIs, migrations, performance requirements
- Prioritization: document reasoning per factor
- Edge cases documented with same rigor as happy path
- PRD versioning with changelog

## Verification Checklist

- Each user story is estimable; small enough for one sprint; acceptance criteria unambiguous
- Success metrics: instrumented; analysis query feasible
- Prioritization: consistent with strategic priorities
- Cross-functional walkthrough (engineering, design, QA, support) with documented resolutions
- Scope boundaries confirmed with stakeholders
- Rollout plan includes specific rollback criteria and monitoring checkpoints