prd-management

What problem does it solves?

Managing Product Requirements Documents (PRDs) and Feature Requirements Documents (FRDs) with consistent naming, structured organization, and clear status tracking is essential for effective product development. Inconsistent PRD management leads to confusion and delays. This Skill automates PRD lifecycle management.

Core Features & Use Cases

• Naming Conventions: Automatic application of standard naming for full product PRDs, feature PRDs, and task lists.
• Directory Structure: Maintenance of an organized product-docs/ structure with active/, review/, approved/, and archive/ subdirectories.
• Status Lifecycle: Enforcement of a clear PRD status workflow (DRAFT → REVIEW → APPROVED → ACTIVE → COMPLETE → ARCHIVED) with validation of transitions.
• Required Metadata: Ensures all PRDs include essential information like status, version, author, and approval details.
• PRD-to-Task Linking: Establishes clear traceability between PRDs and their corresponding implementation task lists.
• Use Case: Creating a new feature PRD, moving a PRD from DRAFT to APPROVED, linking a PRD to its implementation task list, archiving a completed PRD, or auditing PRDs for completeness.

Quick Start

Use the prd-management skill to generate a template for a new feature PRD, including all required metadata and sections.