From product-design
Manages PRD lifecycle: applies naming conventions, maintains directory structure, enforces status transitions, links PRDs to tasks, runs quality checks, and automates archiving.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-design:prd-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking.
This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking.
When this skill activates, Claude will automatically:
Apply PRD Naming Conventions
<product-name>-prd.md<feature-name>-frd.md<feature-name>-simple-frd.md<prd-name>-tasks.mdMaintain Directory Structure
product-docs/
├── prds/
│ ├── active/ # Currently being implemented
│ │ ├── product-prds/ # Full product PRDs
│ │ └── feature-prds/ # Feature-specific PRDs
│ ├── review/ # Under review/approval
│ ├── approved/ # Approved, awaiting implementation
│ └── archive/ # Completed/deprecated
├── personas/ # User personas
├── positioning/ # Product positioning docs
└── tasks/ # Generated task lists
Enforce Status Lifecycle
Include Required Metadata
---
status: DRAFT
version: 1.0
created: YYYY-MM-DD
last_updated: YYYY-MM-DD
author:
approved_by:
approved_date:
task_file: ./tasks/<name>-tasks.md
---
When creating or updating PRDs:
In the PRD, add Implementation Tracking section:
## Implementation Tracking
Task List: ./tasks/<filename>-tasks.md
Generated: YYYY-MM-DD
Status: See task file for current progress
In task files, reference source PRD:
Source PRD: ../prds/active/<filename>.md
Generated: YYYY-MM-DD
Total Tasks: X
Completed: 0
Before marking any PRD as APPROVED, verify:
Archive PRDs when:
Add archive metadata:
archive_date: YYYY-MM-DD
archive_reason: Implementation complete
final_task_completion: 100%
implementation_duration: X days
npx claudepluginhub jpoutrin/product-forge --plugin product-designAnalyzes feature requests, maintains PRDs, and decomposes into tracks with work breakdowns and execution order. For new feature planning, architecture changes, requirements analysis, or plan adjustments.
Creates a Product Requirements Document (PRD) from scratch. Activates automatically when users say 'let's create a product requirements document' or 'I want to create a new PRD'.