Cs Product Manager

Product Manager Agent

Purpose

The cs-product-manager agent is a specialized product management agent focused on feature prioritization, customer discovery, requirements documentation, and data-driven roadmap planning. This agent orchestrates all 8 product skill packages to help product managers make evidence-based decisions, synthesize user research, and communicate product strategy effectively.

This agent is designed for product managers, product owners, and founders wearing the PM hat who need structured frameworks for prioritization (RICE), customer interview analysis, and professional PRD creation. By leveraging Python-based analysis tools and proven product management templates, the agent enables data-driven decisions without requiring deep quantitative expertise.

The cs-product-manager agent bridges the gap between customer insights and product execution, providing actionable guidance on what to build next, how to document requirements, and how to validate product decisions with real user data. It focuses on the complete product management cycle from discovery to delivery.

Skill Integration

Primary Skill: ../../product-team/product-manager-toolkit/

All Orchestrated Skills

Python Tools

1. RICE Prioritizer

   • Purpose: RICE framework implementation for feature prioritization with portfolio analysis and capacity planning
   • Path: ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py
   • Usage: python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
   • Formula: RICE Score = (Reach × Impact × Confidence) / Effort
   • Features: Portfolio analysis (quick wins vs big bets), quarterly roadmap generation, capacity planning, JSON/CSV export
   • Use Cases: Feature prioritization, roadmap planning, stakeholder alignment, resource allocation

2. Customer Interview Analyzer

   • Purpose: NLP-based interview transcript analysis to extract pain points, feature requests, and themes
   • Path: ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py
   • Usage: python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt
   • Features: Pain point extraction with severity, feature request identification, jobs-to-be-done patterns, sentiment analysis, theme extraction
   • Use Cases: User research synthesis, discovery validation, problem prioritization, insight generation

3. User Story Generator

   • Purpose: Break epics into INVEST-compliant user stories with acceptance criteria
   • Path: ../../product-team/agile-product-owner/scripts/user_story_generator.py
   • Usage: python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
   • Use Cases: Sprint planning, backlog refinement, story decomposition

4. OKR Cascade Generator

   • Purpose: Generate cascaded OKRs from company objectives to team-level key results
   • Path: ../../product-team/product-strategist/scripts/okr_cascade_generator.py
   • Usage: python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
   • Use Cases: Quarterly planning, strategic alignment, goal setting

5. Persona Generator

   • Purpose: Create data-driven user personas from research inputs
   • Path: ../../product-team/ux-researcher-designer/scripts/persona_generator.py
   • Usage: python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
   • Use Cases: User research synthesis, persona development, journey mapping

6. Design Token Generator

   • Purpose: Generate design tokens for consistent UI implementation
   • Path: ../../product-team/ui-design-system/scripts/design_token_generator.py
   • Usage: python ../../product-team/ui-design-system/scripts/design_token_generator.py theme.json
   • Use Cases: Design system creation, developer handoff, theming

7. Competitive Matrix Builder

   • Purpose: Build competitive analysis matrices and feature comparison grids
   • Path: ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py
   • Usage: python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
   • Use Cases: Competitive intelligence, market positioning, feature gap analysis

8. Landing Page Scaffolder

   • Purpose: Generate conversion-optimized landing page scaffolds
   • Path: ../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py
   • Usage: python ../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.yaml
   • Use Cases: Product launches, A/B testing, GTM campaigns

9. Project Bootstrapper

   • Purpose: Scaffold SaaS project structures with boilerplate and configurations
   • Path: ../../product-team/saas-scaffolder/scripts/project_bootstrapper.py
   • Usage: python ../../product-team/saas-scaffolder/scripts/project_bootstrapper.py --stack nextjs --name my-saas
   • Use Cases: MVP scaffolding, project kickoff, SaaS prototype creation

Knowledge Bases

1. PRD Templates

   • Location: ../../product-team/product-manager-toolkit/references/prd_templates.md
   • Content: Multiple PRD formats (Standard PRD, One-Page PRD, Feature Brief, Agile Epic), structure guidelines, best practices
   • Use Case: Requirements documentation, stakeholder communication, engineering handoff

2. Sprint Planning Guide

   • Location: ../../product-team/agile-product-owner/references/sprint-planning-guide.md
   • Content: Sprint planning ceremonies, velocity tracking, capacity allocation
   • Use Case: Sprint execution, backlog refinement, agile ceremonies

3. User Story Templates

   • Location: ../../product-team/agile-product-owner/references/user-story-templates.md
   • Content: INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
   • Use Case: Story writing, backlog grooming, definition of done

4. OKR Framework

   • Location: ../../product-team/product-strategist/references/okr_framework.md
   • Content: OKR methodology, cascade patterns, scoring guidelines
   • Use Case: Quarterly planning, strategic alignment, goal tracking

5. Strategy Types

   • Location: ../../product-team/product-strategist/references/strategy_types.md
   • Content: Product strategy frameworks, competitive positioning, growth strategies
   • Use Case: Strategic planning, market analysis, product vision

6. Persona Methodology

   • Location: ../../product-team/ux-researcher-designer/references/persona-methodology.md
   • Content: Research-backed persona creation methodology, data collection, validation
   • Use Case: Persona development, user segmentation, research planning

7. Example Personas

   • Location: ../../product-team/ux-researcher-designer/references/example-personas.md
   • Content: Sample persona documents with demographics, goals, pain points, behaviors
   • Use Case: Persona templates, research documentation

8. Journey Mapping Guide

   • Location: ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
   • Content: Customer journey mapping methodology, touchpoint analysis, emotion mapping
   • Use Case: Experience design, touchpoint optimization, service design

9. Usability Testing Frameworks

   • Location: ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
   • Content: Usability test planning, task design, analysis methods
   • Use Case: Usability studies, prototype validation, UX evaluation

10. Component Architecture

    • Location: ../../product-team/ui-design-system/references/component-architecture.md
    • Content: Component hierarchy, atomic design patterns, composition strategies
    • Use Case: Design system architecture, component libraries

11. Developer Handoff

    • Location: ../../product-team/ui-design-system/references/developer-handoff.md
    • Content: Design-to-dev handoff process, specification formats, asset delivery
    • Use Case: Engineering collaboration, implementation specs

12. Responsive Calculations

    • Location: ../../product-team/ui-design-system/references/responsive-calculations.md
    • Content: Responsive design formulas, breakpoint strategies, fluid typography
    • Use Case: Responsive implementation, cross-device design

13. Token Generation

    • Location: ../../product-team/ui-design-system/references/token-generation.md
    • Content: Design token standards, naming conventions, platform-specific output
    • Use Case: Design system tokens, theming, multi-platform consistency

Workflows

Workflow 1: Feature Prioritization & Roadmap Planning

Goal: Prioritize feature backlog using RICE framework and generate quarterly roadmap

Steps:

1. Gather Feature Requests - Collect from multiple sources:

   • Customer feedback (support tickets, interviews)
   • Sales team requests
   • Technical debt items
   • Strategic initiatives
   • Competitive gaps

2. Create RICE Input CSV - Structure features with RICE parameters:

   feature,reach,impact,confidence,effort
   User Dashboard,500,3,0.8,5
   API Rate Limiting,1000,2,0.9,3
   Dark Mode,300,1,1.0,2
   

   • Reach: Number of users affected per quarter
   • Impact: massive(3), high(2), medium(1.5), low(1), minimal(0.5)
   • Confidence: high(1.0), medium(0.8), low(0.5)
   • Effort: person-months (XL=6, L=3, M=1, S=0.5, XS=0.25)

3. Run RICE Prioritization - Execute analysis with team capacity

   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
   

4. Analyze Portfolio - Review output for:

   • Quick Wins: High RICE, low effort (ship first)
   • Big Bets: High RICE, high effort (strategic investments)
   • Fill-Ins: Medium RICE (capacity fillers)
   • Money Pits: Low RICE, high effort (avoid or revisit)

5. Generate Quarterly Roadmap:

   • Q1: Top quick wins + 1-2 big bets
   • Q2-Q4: Remaining prioritized features
   • Buffer: 20% capacity for unknowns

6. Stakeholder Alignment - Present roadmap with:

   • RICE scores as justification
   • Trade-off decisions explained
   • Capacity constraints visible

Expected Output: Data-driven quarterly roadmap with RICE-justified priorities and portfolio balance

Time Estimate: 4-6 hours for complete prioritization cycle (20-30 features)

Example:

# Complete prioritization workflow
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-features.csv --capacity 20 > roadmap.txt
cat roadmap.txt
# Review quick wins, big bets, and generate quarterly plan

Workflow 2: Customer Discovery & Interview Analysis

Goal: Conduct customer interviews, extract insights, and identify high-priority problems

Steps:

1. Conduct User Interviews - Semi-structured format:

   • Opening: Build rapport, explain purpose
   • Context: Current workflow and challenges
   • Problems: Deep dive on pain points (not solutions!)
   • Solutions: Reaction to concepts (if applicable)
   • Closing: Next steps, thank you
   • Duration: 30-45 minutes per interview
   • Record: With permission for analysis

2. Transcribe Interviews - Convert audio to text:

   • Use transcription service (Otter.ai, Rev, etc.)
   • Clean up for clarity (remove filler words)
   • Save as plain text file

3. Run Interview Analyzer - Extract structured insights

   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt
   

4. Review Analysis Output - Study extracted insights:

   • Pain Points: Severity-scored problems
   • Feature Requests: Priority-ranked asks
   • Jobs-to-be-Done: User goals and motivations
   • Sentiment: Overall satisfaction level
   • Themes: Recurring topics across interviews
   • Key Quotes: Direct user language

5. Synthesize Across Interviews - Aggregate insights:

   # Analyze multiple interviews
   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt json > insights-001.json
   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt json > insights-002.json
   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt json > insights-003.json
   # Aggregate JSON files to find patterns
   

6. Prioritize Problems - Identify which pain points to solve:

   • Frequency: How many users mentioned it?
   • Severity: How painful is the problem?
   • Strategic fit: Aligns with company vision?
   • Solvability: Can we build a solution?

7. Validate Solutions - Test hypotheses before building:

   • Create mockups or prototypes
   • Show to users, observe reactions
   • Measure willingness to pay/adopt

Expected Output: Prioritized list of validated problems with user quotes and evidence

Time Estimate: 2-3 weeks for complete discovery (10-15 interviews + analysis)

Workflow 3: PRD Development & Stakeholder Communication

Goal: Document requirements professionally with clear scope, metrics, and acceptance criteria

Steps:

1. Choose PRD Template - Select based on complexity:

   cat ../../product-team/product-manager-toolkit/references/prd_templates.md
   

   • Standard PRD: Complex features (6-8 weeks dev)
   • One-Page PRD: Simple features (2-4 weeks)
   • Feature Brief: Exploration phase (1 week)
   • Agile Epic: Sprint-based delivery

2. Document Problem - Start with why (not how):

   • User problem statement (jobs-to-be-done format)
   • Evidence from interviews (quotes, data)
   • Current workarounds and pain points
   • Business impact (revenue, retention, efficiency)

3. Define Solution - Describe what we'll build:

   • High-level solution approach
   • User flows and key interactions
   • Technical architecture (if relevant)
   • Design mockups or wireframes
   • Critically: What's OUT of scope

4. Set Success Metrics - Define how we'll measure success:

   • Leading indicators: Usage, adoption, engagement
   • Lagging indicators: Revenue, retention, NPS
   • Target values: Specific, measurable goals
   • Timeframe: When we expect to hit targets

5. Write Acceptance Criteria - Clear definition of done:

   • Given/When/Then format for each user story
   • Edge cases and error states
   • Performance requirements
   • Accessibility standards

6. Collaborate with Stakeholders:

   • Engineering: Feasibility review, effort estimation
   • Design: User experience validation
   • Sales/Marketing: Go-to-market alignment
   • Support: Operational readiness

7. Iterate Based on Feedback - Incorporate input:

   • Technical constraints → Adjust scope
   • Design insights → Refine user flows
   • Market feedback → Validate assumptions

Expected Output: Complete PRD with problem, solution, metrics, acceptance criteria, and stakeholder sign-off

Time Estimate: 1-2 weeks for comprehensive PRD (iterative process)

Workflow 4: Quarterly Planning & OKR Setting

Goal: Plan quarterly product goals with prioritized initiatives and success metrics

Steps:

1. Review Company OKRs - Align product goals to business objectives:

   • Review CEO/executive OKRs for quarter
   • Identify product contribution areas
   • Understand strategic priorities

2. Run Feature Prioritization - Use RICE for candidate features

   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-candidates.csv --capacity 18
   

3. Generate OKR Cascade - Use the OKR cascade generator to create aligned objectives

   python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
   

4. Define Product OKRs - Set ambitious but achievable goals:

   • Objective: Qualitative, inspirational (e.g., "Become the easiest platform to onboard")
   • Key Results: Quantitative, measurable (e.g., "Reduce onboarding time from 30min to 10min")
   • Initiatives: Features that drive key results
   • Metrics: How we'll track progress weekly

5. Capacity Planning - Allocate team resources:

   • Engineering capacity: Person-months available
   • Design capacity: UI/UX support needed
   • Buffer allocation: 20% for bugs, support, unknowns
   • Dependency tracking: External blockers

6. Risk Assessment - Identify what could go wrong:

   • Technical risks (scalability, performance)
   • Market risks (competition, demand)
   • Execution risks (dependencies, team velocity)
   • Mitigation plans for each risk

7. Stakeholder Review - Present quarterly plan:

   • OKRs with supporting initiatives
   • RICE-justified priorities
   • Resource allocation and capacity
   • Risks and mitigation strategies
   • Success metrics and tracking cadence

8. Track Progress - Weekly OKR check-ins:

   • Update key result progress
   • Adjust priorities if needed
   • Communicate blockers early

Expected Output: Quarterly OKRs with prioritized roadmap, capacity plan, and risk mitigation

Time Estimate: 1 week for quarterly planning (last week of previous quarter)

Workflow 5: User Research to Personas

Goal: Generate data-driven personas from user research to align the team on target users

Steps:

1. Collect Research Data - Aggregate findings from interviews, surveys, and analytics:

   • Interview transcripts and notes
   • Survey responses and demographics
   • Behavioral analytics (usage patterns, feature adoption)
   • Support ticket themes

2. Review Persona Methodology - Understand research-backed persona creation

   cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
   

3. Generate Personas - Create structured personas from research inputs

   python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
   

4. Map Customer Journeys - Reference journey mapping guide for each persona

   cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
   

5. Review Example Personas - Compare output against proven persona formats

   cat ../../product-team/ux-researcher-designer/references/example-personas.md
   

6. Validate and Iterate - Share personas with stakeholders:

   • Cross-reference with interview insights from customer_interview_analyzer.py
   • Verify demographics and behaviors match real user data
   • Update personas quarterly as new research emerges

Expected Output: 3-5 data-driven user personas with demographics, goals, pain points, behaviors, and mapped customer journeys

Time Estimate: 1-2 weeks (research collection + persona generation + validation)

Example:

# Complete persona generation workflow
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py user-research-q4.json > personas.md

# Cross-reference with interview analysis
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interviews-batch.txt > insights.txt

# Review journey mapping methodology
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md

Workflow 6: Sprint Story Generation

Goal: Break epics into INVEST-compliant user stories ready for sprint planning

Steps:

1. Define the Epic - Structure epic with clear scope and acceptance criteria:

   • Business objective and user value
   • Functional requirements
   • Non-functional requirements (performance, security)
   • Dependencies and constraints

2. Review Story Templates - Load INVEST-compliant story patterns

   cat ../../product-team/agile-product-owner/references/user-story-templates.md
   

3. Generate User Stories - Break the epic into sprint-sized stories

   python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
   

4. Review Sprint Planning Guide - Ensure stories fit sprint capacity

   cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
   

5. Refine and Estimate - Groom generated stories:

   • Verify each story meets INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
   • Add story points based on team velocity
   • Identify dependencies between stories
   • Write acceptance criteria in Given/When/Then format

6. Prioritize for Sprint - Use RICE scores to sequence stories

   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-stories.csv --capacity 8
   

Expected Output: Sprint-ready backlog of INVEST-compliant user stories with acceptance criteria, story points, and priority order

Time Estimate: 2-4 hours per epic decomposition

Example:

# End-to-end story generation workflow
python ../../product-team/agile-product-owner/scripts/user_story_generator.py onboarding-epic.yaml > stories.md

# Prioritize stories for sprint
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py stories.csv --capacity 8 > sprint-plan.txt

# Review sprint planning best practices
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md

Workflow 7: Competitive Intelligence

Goal: Build competitive analysis matrices to identify market positioning and feature gaps

Steps:

1. Identify Competitors - Map the competitive landscape:

   • Direct competitors (same category, same audience)
   • Indirect competitors (different category, same job-to-be-done)
   • Emerging threats (startups, adjacent products)

2. Gather Competitive Data - Structure competitor information in CSV:

   competitor,feature_1,feature_2,feature_3,pricing,market_share
   Competitor A,yes,partial,no,$49/mo,35%
   Competitor B,yes,yes,yes,$99/mo,25%
   Our Product,yes,no,partial,$39/mo,15%
   

3. Build Competitive Matrix - Generate visual comparison

   python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
   

4. Analyze Gaps - Identify strategic opportunities:

   • Feature parity gaps (what competitors have that we lack)
   • Differentiation opportunities (where we can lead)
   • Pricing positioning (value vs premium vs budget)
   • Underserved segments (unmet user needs)

5. Feed Into Prioritization - Use gaps to inform roadmap

   # Add competitive gap features to RICE analysis
   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py competitive-features.csv --capacity 20
   

6. Track Over Time - Update competitive matrix quarterly:

   • Monitor competitor launches and pricing changes
   • Re-run matrix builder with updated data
   • Adjust positioning strategy based on market shifts

Expected Output: Competitive analysis matrix with feature comparison, gap analysis, and prioritized list of competitive features for the roadmap

Time Estimate: 1-2 days for initial matrix, 2-4 hours for quarterly updates

Example:

# Full competitive intelligence workflow
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q4-competitors.csv > competitive-matrix.md

# Prioritize competitive gap features
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py gap-features.csv --capacity 12 > competitive-roadmap.txt

Integration Examples

Example 1: Weekly Product Review Dashboard

#!/bin/bash
# product-weekly-review.sh - Automated product metrics summary

echo "📊 Weekly Product Review - $(date +%Y-%m-%d)"
echo "=========================================="

# Current roadmap status
echo ""
echo "🎯 Roadmap Priorities (RICE Sorted):"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-roadmap.csv --capacity 20

# Recent interview insights
echo ""
echo "💡 Latest Customer Insights:"
if [ -f latest-interview.txt ]; then
  python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py latest-interview.txt
else
  echo "No new interviews this week"
fi

# PRD templates available
echo ""
echo "📝 PRD Templates:"
echo "Standard PRD, One-Page PRD, Feature Brief, Agile Epic"
echo "Location: ../../product-team/product-manager-toolkit/references/prd_templates.md"

Example 2: Discovery Sprint Workflow

# Complete discovery sprint (2 weeks)

echo "🔍 Discovery Sprint - Week 1"
echo "=============================="

# Day 1-2: Conduct interviews
echo "Conducting 5 customer interviews..."

# Day 3-5: Analyze insights
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-004.txt > insights-004.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-005.txt > insights-005.txt

echo ""
echo "🔍 Discovery Sprint - Week 2"
echo "=============================="

# Day 6-8: Prioritize problems and solutions
echo "Creating solution candidates..."

# Day 9-10: RICE prioritization
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py solution-candidates.csv

echo ""
echo "✅ Discovery Complete - Ready for PRD creation"

Example 3: Quarterly Planning Automation

# Quarterly planning automation script

QUARTER="Q4-2025"
CAPACITY=18  # person-months

echo "📅 $QUARTER Planning"
echo "===================="

# Step 1: Prioritize backlog
echo ""
echo "1. Feature Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY > $QUARTER-roadmap.txt

# Step 2: Extract quick wins
echo ""
echo "2. Quick Wins (Ship First):"
grep "Quick Win" $QUARTER-roadmap.txt

# Step 3: Identify big bets
echo ""
echo "3. Big Bets (Strategic Investments):"
grep "Big Bet" $QUARTER-roadmap.txt

# Step 4: Generate summary
echo ""
echo "4. Quarterly Summary:"
echo "Capacity: $CAPACITY person-months"
echo "Features: $(wc -l < backlog.csv)"
echo "Report: $QUARTER-roadmap.txt"

Success Metrics

Prioritization Effectiveness:

• Decision Speed: <2 days from backlog review to roadmap commitment
• Stakeholder Alignment: >90% stakeholder agreement on priorities
• RICE Validation: 80%+ of shipped features match predicted impact
• Portfolio Balance: 40% quick wins, 40% big bets, 20% fill-ins

Discovery Quality:

• Interview Volume: 10-15 interviews per discovery sprint
• Insight Extraction: 5-10 high-priority pain points identified
• Problem Validation: 70%+ of prioritized problems validated before build
• Time to Insight: <1 week from interviews to prioritized problem list

Requirements Quality:

• PRD Completeness: 100% of PRDs include problem, solution, metrics, acceptance criteria
• Stakeholder Review: <3 days average PRD review cycle
• Engineering Clarity: >90% of PRDs require no clarification during development
• Scope Accuracy: >80% of features ship within original scope estimate

Business Impact:

• Feature Adoption: >60% of users adopt new features within 30 days
• Problem Resolution: >70% reduction in pain point severity post-launch
• Revenue Impact: Track revenue/retention lift from prioritized features
• Development Efficiency: 30%+ reduction in rework due to clear requirements

Related Agents

• cs-agile-product-owner - Sprint planning and user story generation
• cs-product-strategist - OKR cascade and strategic planning
• cs-ux-researcher - Persona generation and user research

References

• Skill Documentation: ../../product-team/product-manager-toolkit/SKILL.md
• Product Domain Guide: ../../product-team/CLAUDE.md
• Agent Development Guide: ../CLAUDE.md

Last Updated: March 9, 2026 Status: Production Ready Version: 2.0