Menu
Templates and Tools

PRD Template

PRD Template

A battle-tested Product Requirements Document template optimized for MSP workflows. This template ensures your projects start with clear direction and maintain context throughout development.

Why This PRD Template?

Traditional PRDs fail in the context engineering era because they:

  • Become stale immediately after writing
  • Lack integration with development workflow
  • Don't track implementation progress
  • Lose connection to actual decisions made

This MSP-optimized PRD template:

  • Lives alongside your code in version control
  • Integrates with Linear for epic/task management
  • Tracks progress through MSP sessions
  • Links to decisions in your knowledge graph

The MSP PRD Template

# [PROJECT NAME] - PRODUCT REQUIREMENTS DOCUMENT

## PROJECT METADATA
- **Project Code**: [XXX-2025]
- **MSP Project ID**: [msp-project-name]
- **Team**: [Team Name]
- **Target Date**: [Q2 2025]
- **Current Progress**: [0%]
- **Status**: [Planning/Active/Complete]

## EXECUTIVE SUMMARY

### Problem Statement
[2-3 sentences clearly defining the problem we're solving]

### Solution Overview
[Brief description of the proposed solution]

### Success Metrics
1. [Specific, measurable outcome]
2. [Another measurable outcome]
3. [Business impact metric]

### Target Users
- **Primary**: [Main user group]
- **Secondary**: [Additional users]

## MSP TRACKING

### Session Command
\`\`\`powershell
# Start working on this project
msp route --project "[XXX-2025]" --prd "[this-file-path]"
msp start --type "feature"
\`\`\`

### Progress Milestones
- [ ] 0-10%: Planning & Research
- [ ] 10-20%: Technical Architecture
- [ ] 20-30%: Core Implementation
- [ ] 30-50%: Feature Development
- [ ] 50-70%: Integration & Testing
- [ ] 70-85%: Beta/UAT
- [ ] 85-95%: Launch Preparation
- [ ] 95-100%: Launch & Monitoring

### Decision Log
<!-- Decisions will be tracked here automatically via MSP -->
<!-- Run: msp decisions --project XXX-2025 --format markdown -->

## REQUIREMENTS

### Functional Requirements

#### [FR1] Core Feature Name
- **Priority**: P0/P1/P2
- **Description**: [What it does]
- **Acceptance Criteria**:
  - [ ] [Specific testable criterion]
  - [ ] [Another criterion]
- **MSP Tracking**: `msp update "Implemented FR1" 25`

#### [FR2] Another Feature
- **Priority**: P1
- **Description**: [What it does]
- **Acceptance Criteria**:
  - [ ] [Criterion]
- **MSP Tracking**: `msp update "Completed FR2" 35`

### Non-Functional Requirements

#### [NFR1] Performance
- **Requirement**: [e.g., <200ms response time]
- **Measurement**: [How to measure]
- **MSP Tracking**: `msp update "Performance optimization" 45`

#### [NFR2] Security
- **Requirement**: [Security standard]
- **Compliance**: [Any compliance needs]

### Technical Requirements

#### Architecture Decisions
<!-- Link to ADRs in your knowledge graph -->
- Database: `msp decide "Using PostgreSQL" --tag architecture`
- API Style: `msp decide "REST over GraphQL" --tag architecture`
- Deployment: `msp decide "Kubernetes on AWS" --tag infrastructure`

## EPIC BREAKDOWN

### Epic Structure for Linear

#### Epic 1: User Research & Validation
- **Description**: [Understand user needs and validate approach]
- **Acceptance Criteria**: [Validated product-market fit]
- **Story Points**: 20
- **MSP Integration**:
  \`\`\`powershell
  msp route --epic "User Research" --progress 10
  \`\`\`

#### Epic 2: Technical Architecture
- **Description**: [Design system architecture]
- **Acceptance Criteria**: [Approved architecture]
- **Story Points**: 30
- **Sub-tasks**:
  - [ ] Design data model
  - [ ] Define API specifications
  - [ ] Plan infrastructure
  - [ ] Security review

#### Epic 3: Core Development
- **Description**: [Build core functionality]
- **Story Points**: 50
- **Sub-tasks**:
  - [ ] [Specific development task]
  - [ ] [Another task]

[Continue with remaining epics...]

## IMPLEMENTATION PLAN

### Phase 1: Foundation (Weeks 1-2)
\`\`\`powershell
# Track phase progress
msp update "Phase 1: Database schema complete" 5
msp update "Phase 1: API design complete" 10
\`\`\`

### Phase 2: Core Features (Weeks 3-6)
- Build [Feature 1]
- Implement [Feature 2]
- Integration testing

### Phase 3: Polish & Launch (Weeks 7-8)
- Performance optimization
- Security audit
- Documentation
- Launch preparation

## RISKS & MITIGATIONS

### Technical Risks
1. **Risk**: [Description]
   - **Impact**: High/Medium/Low
   - **Mitigation**: [Strategy]
   - **MSP Track**: `msp decide "Mitigation: [approach]" --tag risk`

### Business Risks
1. **Risk**: [Market timing]
   - **Impact**: Medium
   - **Mitigation**: [Phased rollout]

## DEPENDENCIES

### External Dependencies
- [ ] API Integration: [Service name]
- [ ] Third-party library: [Library]

### Internal Dependencies
- [ ] Team X: [What we need from them]
- [ ] Platform feature: [Required capability]

## APPENDICES

### A. Mockups & Designs
- [Link to Figma]
- [Link to wireframes]

### B. Technical Specifications
- [API Spec](./api-spec.md)
- [Database Schema](./db-schema.md)

### C. Research & References
- [User Research Doc]
- [Competitive Analysis]

---

## MSP INTEGRATION COMMANDS

### Daily Workflow
\`\`\`powershell
# Start day
msp recall --project "XXX-2025"
msp start

# During work
msp update "Completed user auth flow" 32
msp decide "Using OAuth2 for third-party integration"

# End day
msp end --summary "Finished authentication module"
\`\`\`

### Weekly Sync
\`\`\`powershell
# Generate weekly report
msp report --project "XXX-2025" --period week

# Update PRD progress
msp prd update --file "this-prd.md" --progress 32
\`\`\`

### Context for AI
\`\`\`powershell
# Export PRD + context for AI assistance
msp context --include-prd --project "XXX-2025" | clip
\`\`\`

---

*Last Updated: [Date] | Progress: [X%] | [Link to Linear Project]*

Using the PRD Template

1. Initial Setup

# Create new project with PRD
msp project create "My Awesome Feature" --template prd

# This creates:
# - PRD document from template
# - Linear project with epics
# - Neo4j project node
# - Obsidian project folder

The PRD template is designed to map directly to Linear's structure:

PRD Section → Linear Mapping:
  Executive Summary → Project Description
  Epic Breakdown → Linear Epics
  Sub-tasks → Linear Issues
  Success Metrics → Project Goals
  Progress Milestones → Cycles/Sprints

3. Track Progress

# Update PRD automatically
msp prd sync

# This updates:
# - Progress percentage from sessions
# - Decision log from Neo4j
# - Completed tasks from Linear
# - Risk status

4. Generate Reports

# Weekly status from PRD
msp prd report --weekly

# Outputs:
# - Progress this week
# - Decisions made
# - Risks identified
# - Upcoming milestones

PRD Best Practices

1. Keep It Living

  • Update progress in real-time via MSP
  • Review and revise requirements as you learn
  • Link all decisions back to the PRD
  • Use version control for PRD changes

2. Integration Points

<!-- In your PRD -->

### Latest Decisions
<!-- Auto-updated by MSP -->
{{msp_decisions project="XXX-2025" limit=10}}

### Current Progress
<!-- Auto-updated by MSP -->
{{msp_progress project="XXX-2025" visual=true}}

### Active Blockers
<!-- Auto-updated by MSP -->
{{msp_blockers project="XXX-2025" status="active"}}

3. Team Collaboration

# Share PRD context
msp prd share --team "backend" --include-context

# Review PRD decisions
msp prd review --with "@teamlead"

# Generate PRD changelog
msp prd changelog --since "last-week"

Advanced PRD Features

Dynamic Sections

### Automated Sections

#### Build Status
{{msp_ci_status project="XXX-2025"}}

#### Test Coverage
{{msp_test_coverage project="XXX-2025"}}

#### Performance Metrics
{{msp_performance baseline="1.0" current="true"}}

Risk Tracking

# Add risk to PRD
msp prd risk add "Third-party API may change" --impact high

# Update risk status
msp prd risk update "API-RISK-001" --status "mitigated"

# Generate risk matrix
msp prd risk matrix --output "risks.png"

Stakeholder Updates

# Generate executive summary
msp prd summary --for "executives" --format "pdf"

# Create progress visualization
msp prd visualize --type "burndown" --output "progress.png"

# Email update
msp prd email --to "stakeholders@company.com" --subject "Weekly PRD Update"

PRD Templates by Project Type

Web Application PRD

Includes sections for:

  • Frontend/Backend split
  • API documentation
  • Database design
  • Deployment strategy

Download Template

Next Steps

  1. Download the template and customize for your needs
  2. Create your first MSP-integrated PRD
  3. Connect to Linear for seamless epic management
  4. Start tracking progress with every session

A good PRD is a compass, not a contract. With MSP integration, it becomes a living guide that evolves with your project.

Templates & Tools

Comprehensive collection of templates, scripts, and tools to accelerate your context engineering workflow. Proven patterns, ready-to-use scripts, IDE integrations, and automation tools for MSP.

Architecture Decision Records (ADR) Templates

Document and track architecture decisions with MSP-optimized ADR templates. Never lose track of why your system is built the way it is with automated decision tracking and knowledge graph integration.