Generate Comprehensive Product Requirements Documents

Planning PRD Agent is an autonomous product requirements specialist that creates comprehensive, actionable PRDs bridging business requirements with technical implementation. It works through five stages: requirements gathering (analyzing existing documentation, user feedback, and business objectives, identifying stakeholders and their needs, researching market context and competitive landscape, and defining success metrics and KPIs), problem definition (articulating the core problem, identifying target user personas and pain points, defining scope boundaries, and establishing business value and impact), solution design (detailed user stories with acceptance criteria, functional and non-functional requirements, UX flows and interactions, and integration requirements and dependencies), technical specification (system architecture and data models, APIs and external integrations, performance, security, and scalability requirements, and technical risks and mitigation), and implementation planning (breaking features into development phases, timeline estimates and milestones, testing and QA requirements, and a rollout strategy with success measurement).

Use it when you need a single document that gives every stakeholder - product, engineering, QA - clear, traceable guidance for building a feature. It is not for vague requirement lists: the agent's own guidelines require measurable criteria and concrete examples, explicit edge-case and error-scenario coverage, and every requirement traced back to a business objective.

Given business requirements and market context, it produces a structured PRD: an executive summary (problem statement, proposed solution, success metrics, timeline overview), user stories in an "As a [user type], I want [functionality] so that [benefit]" format with acceptance criteria covering testable requirements, edge cases, and performance expectations, functional requirements (core features, UI requirements, data management, integration requirements), technical specifications (architecture overview, API specifications, database schema, security requirements, performance benchmarks), and an implementation plan (phase breakdown, dependencies and risks, testing strategy, launch plan).

### Product Requirements Document: [Product Name]

### Executive Summary
- Problem statement
- Proposed solution
- Success metrics
- Timeline overview

### User Stories
**As a [user type], I want [functionality] so that [benefit]**
- Acceptance Criteria:
  - [ ] Specific, testable requirements
  - [ ] Edge cases and error handling
  - [ ] Performance expectations

### Functional Requirements
1. Core Features
2. User Interface Requirements
3. Data Management
4. Integration Requirements

### Technical Specifications
- Architecture overview
- API specifications
- Database schema
- Security requirements
- Performance benchmarks

### Implementation Plan
- Phase breakdown
- Dependencies and risks
- Testing strategy
- Launch plan

Uses a standardized user-story template ("As a [persona] / I want to [action] / So that [outcome]" with Given/When/Then acceptance criteria plus explicit response-time and throughput requirements) and a technical-requirement format (title, description, priority, dependencies, acceptance) to keep specs consistent across features.

Product managers and technical leads who need PRDs that enable confident development decisions - specific and measurable, user-first, covering edge cases and non-functional requirements, planned for scale, and detailed enough to support accurate development estimates and success measurement.