Generate Comprehensive Product Requirements Documents

This agent creates comprehensive, actionable Product Requirements Documents that bridge business strategy with technical implementation, giving all stakeholders clarity on goals, requirements, and success metrics. It starts with stakeholder analysis (identifying users, business, technical, legal, and marketing stakeholders and their needs) and context gathering (existing documentation, competitive landscape, market requirements, technical constraints). Problem definition clearly articulates the problem being solved, user pain points, and the business opportunity. The solution framework defines the proposed approach, key features, and a high-level user journey.

Requirements specification breaks down functional and non-functional requirements with clear acceptance criteria. Success metrics establish measurable KPIs, success criteria, and progress-tracking methods. Risk assessment identifies technical, business, and timeline risks with mitigation strategies. Resource planning estimates development effort, dependencies, and required resources.

The deliverable is a complete PRD covering: an executive summary (problem statement, business justification, solution overview, expected impact, resources and timeline), a product overview (target users/personas, use cases, user stories, success metrics), functional requirements (core features, UI requirements, integrations, data requirements), non-functional requirements (performance/scalability, security/compliance, accessibility/i18n), technical considerations (architecture, third-party dependencies, data migration), an implementation plan (phases, milestones, dependencies, testing strategy), and a risk analysis (technical, business, and timeline risks with mitigations). Individual requirements and user stories follow structured templates with explicit acceptance criteria and priority.

Guidelines followed throughout: specific, measurable language (no vague terms like "user-friendly" or "fast"), every requirement traceable to user value or business need, technical/budget/timeline/regulatory constraints factored in, scale considered as the product grows, edge cases and failure scenarios addressed, all stakeholder concerns represented, objectively testable requirements, and extensibility considered. Every PRD is validated against four questions: What are we building? Why? How will we know if it's successful? What are the risks and how do we mitigate them?

Use this agent when a new feature or product needs a formal PRD that aligns business, user, and technical stakeholders before development starts. It is well suited to initiatives with cross-functional impact where a shared, testable requirements document reduces ambiguity. It is not meant for a trivial change or a well-understood bug fix where a full PRD is overkill - reserve it for work substantial enough to need explicit stakeholder alignment.

Input: the problem/opportunity, stakeholder context, and any existing documentation or competitive research.

Output: a complete PRD document with all standard sections. Example requirement and user story templates the agent uses:

REQ-001: [Requirement Title]
Description: [What needs to be accomplished]
Acceptance Criteria:
- [Specific, testable condition 1]
Priority: [High/Medium/Low]

As a [user type], I want [capability] so that [benefit/value]
Given [context/precondition]
When [action/trigger]
Then [expected outcome]

Produces a standalone PRD document meant to be shared with product, engineering, and business stakeholders; it does not connect to a specific product-management or ticketing tool itself.

Product managers writing formal requirements documents for cross-functional initiatives, and teams that need testable, acceptance-criteria-driven requirements rather than an informal feature description.