prd-structure

When creating or reviewing Product Requirements Documents. Used by PM-AGENT.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill provides a standardized framework for drafting and auditing Product Requirements Documents (PRDs). It streamlines the product planning process by enforcing best practices in problem definition, success metrics, MoSCoW prioritization, and detailed functional requirements to ensure project clarity and cross-functional alignment.

Use Cases

  • New Feature Planning: Using the structured MoSCoW framework to define MVP scope and prioritize features for upcoming development cycles.
  • PRD Quality Assurance: Auditing existing requirement documents against a rigorous verification checklist to identify missing acceptance criteria or non-measurable goals.
  • Stakeholder Alignment: Creating clear goal-and-metric tables to communicate project impact and success criteria to leadership and engineering teams.
  • Technical Specification Drafting: Defining detailed functional and non-functional requirements with specific performance targets to guide development and QA teams.
nameprd-structure
descriptionWhen creating or reviewing Product Requirements Documents. Used by PM-AGENT.
version1.0.0
tokens~400
confidencehigh
- https//www.atlassian.com/agile/product-management/requirements
last_validated2025-01-10
next_review2025-01-24
tags[product, prd, requirements, planning]

When to Use

When creating or reviewing Product Requirements Documents. Used by PM-AGENT.

Patterns

PRD Essential Sections

1. Problem Statement

## Problem
- Current state: {how it works today}
- Pain points: {specific issues}
- Impact: {quantified cost/time/frustration}

2. Goals & Metrics

| Goal | Metric | Target |
|------|--------|--------|
| Reduce support tickets | Tickets/week | -30% |
| Improve conversion | Signup rate | +15% |

3. Scope (MoSCoW)

## MVP (Must Have)
- Feature A
- Feature B

## Should Have (P1)
- Feature C

## Could Have (P2)
- Feature D

## Won't Have (Out of Scope)
- Feature X (reason)

4. Requirements

## Functional Requirements
| ID | Requirement | Priority | AC |
|----|-------------|----------|-----|
| FR-01 | User can login | Must | Given/When/Then |

## Non-Functional Requirements
| ID | Category | Requirement | Target |
|----|----------|-------------|--------|
| NFR-01 | Performance | Response time | <200ms p95 |

Anti-Patterns

  • No measurable success criteria
  • Scope without prioritization
  • Requirements without acceptance criteria
  • Missing constraints/assumptions
  • No "out of scope" section

Verification Checklist

  • Problem quantified (not just described)
  • Success metrics are measurable
  • MoSCoW prioritization complete
  • All requirements have AC
  • Out of scope explicitly listed
  • Assumptions documented