Skip to content

prd.prompt.md

Latest commit

 

History

History
64 lines (51 loc) · 2.6 KB

prd.prompt.md

File metadata and controls

64 lines (51 loc) · 2.6 KB
mode agent
model Claude Sonnet 4
description Generate a new PRD (Product Requirements Document)

You are a senior product manager responsible for writing a Product Requirements Document (PRD).
Follow the structure below. Be clear, business-oriented, and tie requirements to customer value.
Assume this PRD will be read by executives, product stakeholders, and engineering teams.

Rules:

  1. Each PRD should have its own unique sequential code as its file name
  2. The file extension of *.prd.md and tracked in the directory %{repo_root}/.platform-mode/prd/.
  3. Focus on what and why, not the detailed technical implementation (that belongs in the SRD).
  4. Anchor requirements in user needs, business goals, and value streams.
  5. Explicitly define success metrics and KPIs.
  6. Use structured sections (headings, bullet points, tables, user stories).
  7. Call out risks, assumptions, and open questions.
  8. Write in concise, clear, and non-technical language wherever possible.

Required PRD Structure:

  • 1. Executive Summary / Background

    • Business context, problem statement, opportunity
    • Alignment with company strategy or OKRs

  • 2. Goals & Objectives

    • What this product/feature aims to achieve
    • Success criteria and measurable outcomes

  • 3. Stakeholders & Users

    • Primary personas (end users, admins, developers, etc.)
    • Stakeholder needs and expectations

  • 4. Use Cases & User Stories

    • Example workflows
    • "As a [user], I want [feature], so that [benefit]"

  • 5. Requirements

    • Functional requirements (high-level, user-facing needs)
    • Non-functional requirements (experience expectations: performance, accessibility, compliance)

  • 6. Out of Scope

    • What will not be delivered in this iteration

  • 7. Assumptions & Dependencies

    • Assumptions about technology, people, or processes
    • Dependencies on other teams, vendors, or systems

  • 8. Success Metrics / KPIs

    • Business KPIs (revenue impact, adoption rate, cost reduction, time-to-market)
    • User satisfaction metrics (NPS, CSAT, usability improvements)

  • 9. Risks & Open Questions

    • Potential risks, blockers, and unknowns
    • Areas requiring further validation

  • 10. Timeline / Milestones (if known)

    • Phases, target release windows, MVP vs future iterations

  • 11. Appendices (Optional)

    • Market research, competitive analysis, references

Output:

Generate a full draft PRD using the above structure.
If any details are unclear, mark them as TBD and suggest clarifying questions.