Product Requirements Document Research, Development, and Revision Chain

Goal

Provide the user with a complete, stakeholder-ready Product Requirements Document (PRD) that has been researched, drafted, expanded, revised, and quality-checked for clarity, completeness, and alignment with the product’s market and type.

Inputs to gather

• Product name (anchors all subsequent content)
• Target market / user group (guides audience-specific requirements)
• Product type / category (determines industry standards and examples)

Before doing any work, ask the user for these inputs in ONE message. Skip anything they already provided. If they tell you to decide, choose sensible defaults and say what you chose.

Workflow

1. Research current best practices and industry standards for PRDs that apply to the given product type and target market. List typical PRD sections (Objectives, User Stories, Functional Requirements, Non-Functional Requirements, Assumptions, Constraints, Success Metrics) and include brief, relevant insights in a bullet list. Share this research with the user and invite quick feedback before moving on.

2. Draft an initial PRD outline for the product name using the researched sections. Include at minimum:

   1. Executive Summary
   2. Objectives and Goals
   3. Target Audience and User Profiles
   4. Functional Requirements
   5. Non-Functional Requirements
   6. Assumptions and Dependencies
   7. Constraints and Limitations
   8. Success Metrics
      For each numbered section, provide a short purpose statement and bullet hints of expected content. Present the outline to the user for approval or edits.

3. Upon approval, expand every outline section into detailed content. For each section:
   • Write thorough explanations tailored to the product type and target market.
   • List concrete examples and specific requirements.
   • Add questions or prompts that could refine the section in later iterations.
   Use clear headings and subheadings.

4. Review the detailed PRD internally. Identify any gaps, overlaps, or ambiguities. Produce a revised version that:
   • Shows updated wording or structure.
   • Includes bullet-point comments explaining why each change was made and suggestions for further refinement.
   Provide the revised document to the user for commentary.

5. Incorporate user feedback, then perform a final holistic review. Ensure research insights, draft, detailed content, and revisions integrate seamlessly. Confirm the document is clear, organized, and ready for stakeholder distribution. List any final outstanding questions or considerations that should be resolved before formal sign-off.

6. Deliver the finalized PRD and note the agreed-upon next steps for stakeholder review.

Output

A polished PRD document (structured with headings, subheadings, numbered sections, and bullet points) accompanied by:
• A brief changelog or comment appendix summarizing revisions made.
• A final set of outstanding questions or considerations, if any.