Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Deliverable guide
Product Requirements Document (PRD) Deliverable
Deliverable bundle for drafting and reviewing Product Requirements Documents without inventing customer evidence, scope, requirements, metrics, or approvals.
Read the fileWorkflow
Product Requirements Document (PRD) Output Planning
Plan a Product Requirements Document (PRD) deliverable or recommendation with source-backed checks.
Read the fileWorkflow
Product Requirements Document (PRD) Evidence Review
Review Product Requirements Document (PRD) evidence before recommendation or publication.
Read the fileQuality rubric
Product Requirements Document (PRD) Guidance Quality Check
Rubric for checking whether Product Requirements Document (PRD) guidance is source-backed, evidence-scoped, and safe.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on Product Requirements Document (PRD)
- Teams working in software, digital-products, technology
When to use it
- A Product Requirements Document (PRD) draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- Draft PRDs that separate goals, evidence, requirements, open questions, risks, and decision status.
- Review PRDs for missing customer, business, technical, design, analytics, and rollout evidence.
- Prevent PRDs from becoming unsupported commitments or over-detailed pseudo-specs.
What it helps produce
- Product Requirements Document
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Product Requirements Document (PRD) and return Product Requirements Document with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with Atlassian PRD guide, then confirm that the reference is current and applicable. Inspect Product Requirements Document (PRD) Deliverable before drafting.
Context path: bundles/deliverables/product-requirements-document
What the bundle includes
Frameworks
- requirements evidence review
- scope and success criteria review
- stakeholder alignment
Commands
/draft-prd
Evaluations
- Product Requirements Document (PRD) guidance quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- Not a complete Product Requirements Document (PRD) implementation, administration, legal, research, or professional-advice reference.
- Requires user-provided local evidence before final conclusions about Product Requirements Document (PRD) usage, readiness, scoring, configuration, or commitments.
- Does not replace qualified product, design, engineering, data, legal, privacy, security, or administrator review.
Safety notes
- Require confirmation before turning draft requirements into engineering, customer, legal, launch, or roadmap commitments without stakeholder review and evidence.
- Do not claim access to private systems, customer data, workspaces, documents, dashboards, roadmaps, repositories, accounts, or source records unless the user provides evidence or authorized tool access.