Files
skills/public/product-prd-structure-templates.html
zeekayandHanzo Dev 9e10c1c10e Each llms index points at the other two
hanzoskills.com/llms.txt now opens with the install line, the API
reference index and the company index, so an agent that lands on any
one of the three can find the rest.

robots.txt claimed 537 documents while llms.txt counts 920. The number
is gone from robots.txt; llms.txt derives it.

public/ is regenerated from scripts/site.py, which it had fallen
behind: the copy-prompt menu and agent bar were in the generator and
not in the committed pages. tests/site.mjs passes against the result.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 00:27:59 -07:00

568 lines
27 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>product-prd-structure-templates</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/product-prd-structure-templates.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/product-prd-structure-templates">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/product-prd-structure-templates.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>product-prd-structure-templates</h1><p class="lede">PRD document structure, templates, and best practices for product requirements documentation</p><h1>PRD Structure &amp; Templates</h1>
<p><strong>Scope</strong>: Comprehensive guide to PRD formats, sections, templates, and documentation best practices <strong>Lines</strong>: ~320 <strong>Last Updated</strong>: 2025-10-25 <strong>Format Version</strong>: 1.0 (Atomic)</p>
<hr>
<h2>When to Use This Skill</h2>
<p>Activate this skill when:</p>
<ul><li>Writing a new Product Requirements Document from scratch</li><li>Standardizing PRD format across a product team</li><li>Choosing between lightweight and comprehensive PRD templates</li><li>Defining what sections belong in a PRD vs RFC</li><li>Setting up PRD templates in Notion, Confluence, or Google Docs</li><li>Establishing PRD review and approval workflows</li><li>Training PMs or teams on effective PRD writing</li><li>Migrating from informal specs to structured PRDs</li></ul>
<h2>Core Concepts</h2>
<h3>Concept 1: PRD Purpose and Audience</h3>
<p><strong>Primary Goals</strong>:</p>
<ul><li>Align stakeholders on problem, goals, and solution</li><li>Provide engineering with clear requirements for implementation</li><li>Document decisions and rationale for future reference</li><li>Define success metrics and validation criteria</li></ul>
<p><strong>Key Audiences</strong>:</p>
<ul><li>Engineering: needs technical requirements, edge cases, acceptance criteria</li><li>Design: needs user flows, interaction patterns, visual requirements</li><li>Leadership: needs business justification, metrics, timeline</li><li>QA: needs testable criteria, edge cases, validation approach</li><li>Marketing/Sales: needs feature benefits, target users, competitive positioning</li></ul>
<h3>Concept 2: Standard PRD Sections</h3>
<p><strong>Essential Sections</strong> (every PRD must have):</p>
<ul><li><strong>Problem Statement</strong>: What problem are we solving? Why now?</li><li><strong>Goals &amp; Success Metrics</strong>: What does success look like? How do we measure it?</li><li><strong>Requirements</strong>: What must the solution do? (Functional, non-functional, constraints)</li><li><strong>Out of Scope</strong>: What are we explicitly NOT doing?</li></ul>
<p><strong>Common Optional Sections</strong>:</p>
<ul><li>Background/Context: Market research, user insights, competitive analysis</li><li>User Stories/Scenarios: Concrete examples of user workflows</li><li>Design Mocks: Visual representation of solution</li><li>Technical Considerations: Architecture notes, dependencies, risks</li><li>Timeline/Milestones: Key dates, phases, launch plan</li><li>Open Questions: Unresolved items requiring further discussion</li></ul>
<h3>Concept 3: PRD Formats by Use Case</h3>
<p><strong>One-Pager PRD</strong> (1-2 pages):</p>
<ul><li>Use for: Small features, quick experiments, internal tools</li><li>Focus: Problem, proposed solution, success metrics</li><li>Audience: Small team, fast iteration</li></ul>
<p><strong>Lightweight PRD</strong> (3-5 pages):</p>
<ul><li>Use for: Medium features, iterative development, established products</li><li>Focus: Problem, goals, requirements, user stories</li><li>Audience: Cross-functional team, regular cadence</li></ul>
<p><strong>Comprehensive PRD</strong> (10+ pages):</p>
<ul><li>Use for: Major initiatives, new products, complex integrations</li><li>Focus: All sections, detailed analysis, multiple alternatives</li><li>Audience: Leadership, multiple teams, long-term planning</li></ul>
<hr>
<h2>Patterns</h2>
<h3>Pattern 1: One-Pager PRD Template</h3>
<p><strong>When to use</strong>:</p>
<ul><li>Quick iteration, small scope</li><li>Internal tools or experiments</li><li>Well-understood problem space</li></ul>
<pre><code class="lang-markdown"># [Feature Name] - PRD One-Pager
**Author**: [Name] | **Date**: 2025-10-25 | **Status**: Draft
## Problem
What user problem are we solving? Why is this important now?
[2-3 sentences maximum]
## Solution
What are we building to solve this problem?
[3-5 bullet points describing key functionality]
## Success Metrics
How will we know if this succeeded?
- Metric 1: [e.g., 20% increase in user activation]
- Metric 2: [e.g., &lt;5% error rate]
- Metric 3: [e.g., Ship by Q1 2025]
## Requirements
Must-haves for launch:
- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3
## Out of Scope
What we&#x27;re NOT doing (at least not yet):
- Thing 1
- Thing 2</code></pre>
<p><strong>Benefits</strong>:</p>
<ul><li>Fast to write and review</li><li>Forces focus on essentials</li><li>Easy to keep updated</li></ul>
<h3>Pattern 2: Lightweight PRD Template</h3>
<p><strong>Use case</strong>: Standard feature development with established processes</p>
<pre><code class="lang-markdown"># [Feature Name] - PRD
**Author**: [Name] | **Reviewers**: [Names] | **Date**: 2025-10-25
**Status**: Draft | Review | Approved
## Problem Statement
What problem exists today? Who experiences it? Why is it painful?
[Provide context: user quotes, data, competitive gaps]
## Goals
What are we trying to achieve?
1. **Primary Goal**: [e.g., Increase user retention by 15%]
2. **Secondary Goals**: [e.g., Reduce support tickets, improve NPS]
## Success Metrics
How will we measure success?
| Metric | Current | Target | Timeline |
|--------|---------|--------|----------|
| [KPI 1] | [baseline] | [goal] | [date] |
| [KPI 2] | [baseline] | [goal] | [date] |
## User Stories
Who will use this and how?
**As a** [user type]
**I want** [capability]
**So that** [benefit]
[Include 3-5 key user stories]
## Requirements
### Functional Requirements
- [ ] FR1: System must support [capability]
- [ ] FR2: Users can [action]
- [ ] FR3: [Specific behavior]
### Non-Functional Requirements
- [ ] NFR1: Performance: [e.g., &lt;200ms response time]
- [ ] NFR2: Security: [e.g., SOC 2 compliant data handling]
- [ ] NFR3: Accessibility: [e.g., WCAG 2.1 AA]
### Constraints
- Must integrate with [existing system]
- Cannot exceed [budget/timeline]
- Must support [browsers/platforms]
## Out of Scope
What we&#x27;re explicitly NOT doing:
- [Feature/capability that&#x27;s tempting but out of scope]
- [Platform/integration we&#x27;re deferring]
## Open Questions
- [ ] Question 1: [Issue needing resolution]
- [ ] Question 2: [Decision pending stakeholder input]
## Approval
- [ ] Engineering: [Name]
- [ ] Design: [Name]
- [ ] Product Lead: [Name]</code></pre>
<h3>Pattern 3: Comprehensive PRD Template</h3>
<p><strong>Use case</strong>: Major initiatives, new products, complex features</p>
<pre><code class="lang-markdown"># [Product/Feature Name] - Comprehensive PRD
## Document Metadata
- **Author**: [Name, Role]
- **Stakeholders**: [List all reviewers and approvers]
- **Created**: 2025-10-25
- **Last Updated**: 2025-10-25
- **Status**: Draft | In Review | Approved | In Development
- **Version**: 1.0
## Executive Summary
[2-3 paragraph summary of entire PRD for leadership]
## Background &amp; Context
Why are we doing this? What&#x27;s the broader context?
### Market Context
- Competitive landscape
- Market trends
- Customer demand signals
### User Research
- Interview insights (n=X)
- Survey results (n=Y)
- Usage data analysis
## Problem Statement
### Current State
What&#x27;s happening today? What&#x27;s the pain?
### Desired State
What should the experience be?
### Gap Analysis
What&#x27;s missing to get from current to desired state?
## Goals &amp; Objectives
### Business Goals
1. [Revenue, growth, retention goal]
2. [Market positioning goal]
### User Goals
1. [User capability or outcome]
2. [User experience improvement]
### Success Metrics
| Category | Metric | Current | Target | Measurement |
|----------|--------|---------|--------|-------------|
| Business | [KPI] | [value] | [value] | [how] |
| User | [KPI] | [value] | [value] | [how] |
| Operational | [KPI] | [value] | [value] | [how] |
## User Personas &amp; Scenarios
### Primary Persona: [Name]
- **Role**: [Job title]
- **Goals**: [What they want to achieve]
- **Pain Points**: [Current frustrations]
- **Context**: [When/where they&#x27;ll use this]
### User Scenarios
1. **Scenario 1**: [Concrete example walkthrough]
2. **Scenario 2**: [Another key workflow]
## Requirements
### Functional Requirements
#### Core Functionality
- FR1: [Requirement]
- Acceptance: [GIVEN-WHEN-THEN criteria]
- FR2: [Requirement]
- Acceptance: [Criteria]
#### Secondary Features
- FR3: [Nice-to-have capability]
### Non-Functional Requirements
- NFR1: **Performance**: [Specific targets]
- NFR2: **Security**: [Compliance, data handling]
- NFR3: **Scalability**: [Growth expectations]
- NFR4: **Accessibility**: [Standards compliance]
- NFR5: **Localization**: [Languages, regions]
### Technical Constraints
- Must integrate with [system/API]
- Cannot change [existing behavior]
- Must support [platforms/browsers]
## Design &amp; User Experience
[Link to Figma/design files]
### Key User Flows
1. [Flow 1 description with screenshots]
2. [Flow 2 description]
### Design Principles
- Principle 1: [e.g., &quot;Progressive disclosure&quot;]
- Principle 2: [e.g., &quot;Mobile-first&quot;]
## Technical Considerations
### Architecture Notes
[High-level technical approach - collaborate with eng]
### Dependencies
- Internal: [Team/system dependencies]
- External: [Third-party services, APIs]
### Risks &amp; Mitigations
| Risk | Impact | Likelihood | Mitigation |
|------|--------|------------|------------|
| [Risk 1] | High/Med/Low | High/Med/Low | [Plan] |
## Launch &amp; Rollout
### Phases
1. **Alpha** (Week 1-2): Internal testing
2. **Beta** (Week 3-4): 10% of users
3. **GA** (Week 5): Full rollout
### Go-to-Market
- Marketing: [Campaign approach]
- Sales enablement: [Training, materials]
- Support: [Documentation, training]
## Out of Scope
Explicitly NOT included in this PRD:
- [Feature tempting to include but deferred]
- [Platform/integration postponed]
- [Capability for future iteration]
## Open Questions &amp; Decisions
- [ ] **Q1**: [Question requiring answer before approval]
- Decision: [TBD or decided]
- [ ] **Q2**: [Another open item]
## Appendix
### Research Data
[Link to user research, surveys, analytics]
### Competitive Analysis
[Comparison matrix of competitor features]
### Glossary
- **Term 1**: Definition
- **Term 2**: Definition</code></pre>
<h3>Pattern 4: PRD Versioning and Changelog</h3>
<p><strong>Use case</strong>: Tracking changes during review and development</p>
<pre><code class="lang-markdown">## Version History
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.2 | 2025-10-25 | [Name] | Updated success metrics based on eng feedback |
| 1.1 | 2025-10-24 | [Name] | Added technical constraints section |
| 1.0 | 2025-10-23 | [Name] | Initial draft |
## Changelog
- **2025-10-25**: Removed &quot;real-time sync&quot; from scope per eng constraint discussion
- **2025-10-24**: Added NFR for WCAG 2.1 AA compliance per design review</code></pre>
<hr>
<h2>Quick Reference</h2>
<h3>PRD Section Checklist</h3>
<pre><code>Required Sections | Optional Sections
---------------------------|-------------------
Problem Statement | Background/Context
Goals &amp; Success Metrics | User Personas
Requirements (Functional) | Design Mocks
Out of Scope | Technical Notes
| Timeline/Milestones
| Competitive Analysis</code></pre>
<h3>Documentation Tools Comparison</h3>
<pre><code>Tool | Best For | PRD Features
--------------|-----------------------------|--------------
Notion | Startups, flexible workflows| Templates, comments, databases
Confluence | Enterprise, integration | Versioning, permissions, JIRA link
Google Docs | Collaboration, accessibility| Comments, suggestions, easy sharing
Linear | Dev-focused teams | Issue linking, roadmap integration
Markdown+Git | Engineering-led orgs | Version control, code-like workflow</code></pre>
<h3>Key Guidelines</h3>
<pre><code>✅ DO: Write for multiple audiences (eng, design, leadership)
✅ DO: Include concrete success metrics (not &quot;improve UX&quot;)
✅ DO: Be specific about scope AND out-of-scope
✅ DO: Version your PRD and track changes
✅ DO: Link to supporting docs (research, designs, data)
❌ DON&#x27;T: Prescribe technical implementation (that&#x27;s RFC territory)
❌ DON&#x27;T: Write requirements as user stories alone (need acceptance criteria)
❌ DON&#x27;T: Skip the &quot;why&quot; (problem statement is critical)
❌ DON&#x27;T: Make it longer than necessary (choose right template)
❌ DON&#x27;T: Forget to update PRD during development (living document)</code></pre>
<hr>
<h2>Anti-Patterns</h2>
<h3>Critical Violations</h3>
<p>❌ <strong>Solution-First PRD</strong>: Starting with &quot;We&#x27;re building X&quot; without explaining the problem</p>
<pre><code class="lang-markdown"># ❌ NEVER:
## What We&#x27;re Building
We&#x27;re adding a real-time chat feature to the dashboard.
# ✅ CORRECT:
## Problem Statement
Users currently wait 24+ hours for email responses to time-sensitive questions,
causing frustration (NPS -15 for support experience) and 30% of users abandoning
mid-transaction. We need immediate communication for high-stakes workflows.
## Proposed Solution
Real-time chat embedded in dashboard for instant support connection.</code></pre>
<p>❌ <strong>Vague Success Metrics</strong>: &quot;Improve user satisfaction&quot; instead of measurable targets ✅ <strong>Correct approach</strong>: &quot;Increase NPS from 35 to 50 within 2 quarters post-launch&quot;</p>
<h3>Common Mistakes</h3>
<p>❌ <strong>Missing Out-of-Scope Section</strong>: Teams build features you didn&#x27;t intend</p>
<pre><code class="lang-markdown"># ❌ Don&#x27;t: Omit out-of-scope section
[No mention of what&#x27;s NOT included]
# ✅ Correct: Explicitly call out scope boundaries
## Out of Scope
- Real-time collaborative editing (defer to Q2)
- Mobile app support (web-only for v1)
- Integration with Slack (evaluate post-launch)</code></pre>
<p>❌ <strong>Requirements Without Acceptance Criteria</strong>: &quot;System should be fast&quot; ✅ <strong>Better</strong>: &quot;API responses must complete in &lt;200ms for p95 latency (NFR1)&quot;</p>
<p>❌ <strong>Mixing PRD and RFC Concerns</strong>: PRD shouldn&#x27;t specify database schema or API endpoints ✅ <strong>Better</strong>: PRD defines what data is needed; RFC defines how it&#x27;s stored/accessed</p>
<hr>
<h2>Related Skills</h2>
<ul><li><code>prd-requirements-gathering.md</code> - Use before this skill to collect requirements and research</li><li><code>prd-user-stories-acceptance.md</code> - Deep dive on writing effective user stories and acceptance criteria</li><li><code>prd-technical-specifications.md</code> - Bridge between PRD and RFC for technical details</li><li><code>engineering/rfc-structure-format.md</code> - Engineering counterpart for technical design docs</li><li><code>engineering/rfc-technical-design.md</code> - How engineering translates PRD into technical proposals</li></ul>
<hr>
<p><strong>Last Updated</strong>: 2025-10-25 <strong>Format Version</strong>: 1.0 (Atomic)</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/product-prd-structure-templates.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>