PRD lifecycle management with creation, validation, task generation, and archival
Manages the complete lifecycle of Product Requirements Documents from creation through archival.
/plugin marketplace add jpoutrin/product-forge/plugin install product-design@product-forge-marketplacesonnetDescription: Autonomous PRD lifecycle management with creation, validation, task generation, and archival
Type: Autonomous Multi-Step Agent
This agent manages the complete lifecycle of Product Requirements Documents, from creation through implementation tracking to archival.
Invoke this agent when:
Step 1: Gather Requirements
→ Identify PRD type (Product/Feature/Simple Feature)
→ Collect product/feature name
→ Check for existing related PRDs
Step 2: Create PRD Document
→ Apply appropriate template
→ Guide through interactive creation
→ Populate all required sections
→ Save to: prds/review/[name]-[type].md
Step 3: Add Metadata
→ Set status to DRAFT
→ Add creation date and author
→ Generate unique PRD ID
Step 4: Validate Structure
→ Check all required sections present
→ Validate metadata format
→ Identify missing information
→ Report validation results
Step 5: Generate Tasks (Optional)
→ Ask if tasks should be generated
→ Create task list from PRD content
→ Link PRD to task file
→ Save to: tasks/[name]-tasks.md
Step 1: Identify PRD
→ Find PRD by name or path
→ Read current status
→ Display current metadata
Step 2: Validate Transition
→ Check if transition is valid:
DRAFT → REVIEW → APPROVED → ACTIVE → COMPLETE → ARCHIVED
→ Identify blockers
Step 3: Update Status
→ Update metadata in PRD
→ Change last_updated date
→ Add status change comment
Step 4: Move to Correct Directory
→ DRAFT/REVIEW: prds/review/
→ APPROVED: prds/approved/
→ ACTIVE: prds/active/[type]/
→ COMPLETE/ARCHIVED: prds/archive/[year]/
Step 5: Update References
→ Update any linked task files
→ Notify of location change
Step 1: Scan for PRDs
→ Search all directories for *.md files
→ Identify files with PRD structure
→ Parse metadata from each
Step 2: Analyze Organization
→ Check if files are in correct locations
→ Identify misplaced files
→ Find orphaned task files
Step 3: Generate Organization Report
→ List files needing movement
→ Identify validation issues
→ Show recommended actions
Step 4: Execute Organization (with approval)
→ Move files to correct directories
→ Update references
→ Preserve git history
Step 5: Create Summary Report
→ PRDs by status
→ Task linkage status
→ Action items
Step 1: Identify Active PRDs
→ Scan prds/active/ directory
→ Find all PRDs with ACTIVE status
Step 2: Calculate Progress for Each
→ Read linked task file
→ Count total vs completed tasks
→ Calculate percentage
Step 3: Generate Progress Report
┌─────────────────────────────────────────────────────┐
│ PRD Implementation Progress Report │
├─────────────────────────────────────────────────────┤
│ Feature Authentication (TASK-001) │
│ Progress: ████████░░ 80% (8/10 tasks) │
│ Status: ACTIVE | Started: 2025-01-01 │
│ Blocked: 0 | Est. completion: 2025-01-10 │
├─────────────────────────────────────────────────────┤
│ User Dashboard (TASK-002) │
│ Progress: ████░░░░░░ 40% (4/10 tasks) │
│ Status: ACTIVE | Started: 2025-01-05 │
│ Blocked: 1 | Waiting on: API endpoint │
└─────────────────────────────────────────────────────┘
Step 4: Identify Blockers
→ List blocked tasks with reasons
→ Suggest resolution paths
→ Flag overdue items
Step 1: Identify Candidates
→ Find PRDs with COMPLETE status
→ Find inactive PRDs (>90 days no update)
→ Find cancelled projects
Step 2: Prepare Archive Metadata
→ Calculate final completion percentage
→ Compute implementation duration
→ Summarize outcomes
Step 3: Archive PRDs
→ Add archive metadata
→ Move to archive/[year]/[quarter]/[status]/
→ Rename with status suffix
Step 4: Archive Related Files
→ Move completed task files
→ Archive related documentation
→ Update cross-references
Step 5: Generate Archive Report
→ Summary of archived items
→ Lessons learned (if captured)
→ Reference for future projects
product-docs/
├── prds/
│ ├── active/
│ │ ├── product-prds/
│ │ └── feature-prds/
│ ├── review/
│ ├── approved/
│ └── archive/
│ ├── 2025/
│ │ ├── Q1/
│ │ │ ├── completed/
│ │ │ └── cancelled/
│ │ └── Q2/
│ └── 2024/
└── tasks/
DRAFT ─────→ REVIEW ─────→ APPROVED ─────→ ACTIVE ─────→ COMPLETE ─────→ ARCHIVED
│ │
└──────→ ARCHIVED ←───────────┘
(if cancelled)
Before any status change:
⚠️ Issue: PRD validation failed
Missing: Success Metrics section
Options:
1. Add missing section now
2. Proceed anyway (not recommended)
3. Cancel operation
Select: _
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences