Document Types Overview¶

Structured Requirements supports three core document types, each serving a different purpose in the product development lifecycle.

Document Comparison¶

When to Use Each¶

PRD (Product Requirements Document)¶

Use a PRD when you need to:

• Define product features and requirements
• Document user personas and their needs
• Specify success metrics
• Track risks and assumptions
• Align with strategic goals (V2MOM/OKR)

Key sections: Executive Summary, Personas, User Stories, Requirements, Roadmap

MRD (Market Requirements Document)¶

Use an MRD when you need to:

• Analyze market opportunity
• Define target market segments
• Document competitive landscape
• Establish go-to-market strategy
• Define pricing and positioning

Key sections: Market Analysis, Buyer Personas, Competitive Analysis, GTM Strategy

TRD (Technical Requirements Document)¶

Use a TRD when you need to:

• Document system architecture
• Define API specifications
• Specify security requirements
• Plan infrastructure and scaling
• Document integration points

Key sections: Architecture Overview, API Specs, Security, Infrastructure

Document Flow¶

graph LR
    M[MRD] -->|market insight| P[PRD]
    G[Goals<br/>V2MOM/OKR] -->|alignment| P
    P -->|requirements| T[TRD]
    P -->|features| D[Design]
    T -->|specs| E[Engineering]

Typical Workflow¶

1. Market Analysis (MRD) - Identify opportunity and target market
2. Goal Setting (V2MOM/OKR) - Define strategic objectives
3. Product Definition (PRD) - Specify what to build
4. Technical Planning (TRD) - Plan how to build it
5. Implementation - Build and ship

Package Imports¶

import (
    "github.com/grokify/structured-plan/prd"  // Product requirements
    "github.com/grokify/structured-plan/mrd"  // Market requirements
    "github.com/grokify/structured-plan/trd"  // Technical requirements
)

JSON File Conventions¶

Next Steps¶

• PRD Documentation
• MRD Documentation
• TRD Documentation