Skip to content

PRD template

Copy this template to create a Concourse PRD

Replace the frontmatter title and description with the record title and summary.

  • ID: PRD-NNNN
  • Status: Proposed
  • Decision maker: [name]
  • Scope: [apps, packages, or shared capability]
  • Product owner: [name or team]
  • Design owner: [name or team]
  • Engineering owner: [name or team]
  • Last reviewed: YYYY-MM-DD
  • Related issues or projects: [links, or N/A]
  • Related designs: [links, or N/A]
  • Related ADRs: [links, or N/A]
  • Related user documentation: [links, or N/A]

For sections that do not apply, state "Not applicable" and explain why.

Summary

Describe the capability and its value in a short paragraph.

User problem and evidence

State who has the problem, what the problem is, and why it matters. Link to user research, support reports, product data, or other evidence.

Goals and success measures

GoalMeasureTarget or review method
GoalMeasureTarget

Non-goals

  • State what this capability does not aim to solve.

Users and use cases

Use case: Short name

  • Actor: [person or system]
  • Need: [what the actor needs to do]
  • Goal: [why the actor needs it]

Requirements

Use stable story IDs such as PRD-0001-US-01. Copy the block below for each story. Follow the PRD lifecycle for revisions and retired stories.

PRD-NNNN-US-01: Story title

  • Story status: Current
  • Replaces: N/A
  • Replaced by: N/A
  • User need: As a [user], I want [capability], so that [benefit].
  • Requirement: [required product behavior]
  • Done when:
    • [observable outcome]
    • [observable outcome]

Implementation

Summarize the behavior that exists in the current checkout and where it lives. Record verification evidence in the implementation pull request, not here. Use Issues for active task tracking.

Experience and content

Describe the main flow and the outcomes required from the interface. Cover the states that apply:

  • Entry points and main flow
  • Empty, loading, success, and error states
  • User-visible terms and messages
  • Access and permission states
  • Accessibility needs
  • Links to detailed designs

Constraints and dependencies

  • State product, policy, legal, data, platform, or delivery constraints.
  • Link to any ADR that owns a significant technical choice.
  • Link to other product capabilities or outside dependencies.

User documentation

  • Audience: [who needs help]
  • Tasks to explain: [current user tasks]
  • Agreed terms: [user-visible terms]
  • Examples or screenshots needed: [list, or N/A]
  • Published documentation: [links, or N/A]

Use only accepted requirements with verified, delivered behavior as source material for published user documentation. Rewrite the material for users rather than publishing this PRD unchanged.

Revision history

Use this format for each material revision:

- YYYY-MM-DD — PRD-NNNN-US-01, PRD-NNNN-US-02: Summary and reason. Issue or pull request URL

No revisions.

References

  • [Research, policy, issue, design, ADR, or other supporting source]

Adapted from the MPV requirements template.