prd-management
Automatic PRD lifecycle management, organization, and status tracking. Use when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs) for proper naming, directory structure, and status transitions.
When & Why to Use This Skill
This Claude skill automates the end-to-end lifecycle of Product Requirements Documents (PRDs) and Feature Requirements Documents (FRDs). It streamlines project workflows by enforcing standardized naming conventions, maintaining a structured documentation directory, and tracking status transitions from draft to archive. By linking requirements directly to implementation tasks, it ensures high-quality documentation and seamless progress tracking for product teams.
Use Cases
- Standardizing product documentation across teams by enforcing consistent naming conventions and directory structures for PRDs and FRDs.
- Managing the document lifecycle through automated status transitions (Draft, Review, Approved, Active, Complete) to ensure all stakeholders are aligned on progress.
- Bridging the gap between product planning and engineering by automatically generating and linking task lists to source requirement documents.
- Performing quality assurance on product specifications using built-in checklists to verify success metrics, personas, and technical requirements before approval.
- Maintaining a clean and organized workspace by automatically archiving completed or deprecated project documentation based on predefined rules.
| name | prd-management |
|---|---|
| description | Automatic PRD lifecycle management, organization, and status tracking. Use when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs) for proper naming, directory structure, and status transitions. |
PRD Management 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.
Automatic Behaviors
When this skill activates, Claude will automatically:
Apply PRD Naming Conventions
- Full Product PRDs:
<product-name>-prd.md - Feature PRDs:
<feature-name>-frd.md - Simple Feature PRDs:
<feature-name>-simple-frd.md - Task Lists:
<prd-name>-tasks.md
- Full Product PRDs:
Maintain 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 listsEnforce Status Lifecycle
- DRAFT → REVIEW → APPROVED → ACTIVE → COMPLETE → ARCHIVED
- Validate status transitions
- Update metadata on status changes
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 ---
PRD-to-Task Linking
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 progressIn task files, reference source PRD:
Source PRD: ../prds/active/<filename>.md Generated: YYYY-MM-DD Total Tasks: X Completed: 0
Quality Checks
Before marking any PRD as APPROVED, verify:
- Executive summary is clear and concise
- Problem statement is specific and validated
- Success metrics are quantifiable
- User personas are detailed
- Technical requirements are complete
- All required sections are filled
Archival Rules
Archive PRDs when:
- Implementation is 100% complete
- PRD is superseded by newer version
- Project/feature is cancelled
- PRD is over 1 year old and inactive
Add archive metadata:
archive_date: YYYY-MM-DD
archive_reason: Implementation complete
final_task_completion: 100%
implementation_duration: X days