prd-management

PRD lifecycle management automates organization across status stages—DRAFT, REVIEW, APPROVED, ACTIVE, COMPLETE, ARCHIVED—with enforced directory structure (active/, review/, approved/, archive/ subdirectories) and validated transitions. This ensures consistent tracking and prevents status errors.

Standard naming conventions for PRDs, feature PRDs, and task lists enforce consistency across your documentation. The Skill applies these automatically, eliminating manual naming decisions and reducing confusion when referencing documents.

PRD-to-task linking establishes traceability between requirements documents and their corresponding implementation task lists. This creates clear connections so teams know which tasks implement which PRD requirements.

Required metadata includes status, version, author, and approval details. The Skill validates that all PRDs contain this essential information, ensuring completeness and accountability across your product documentation.

Yes. Automated status validation enforces correct workflow transitions and prevents invalid state changes. Combined with consistent naming and directory maintenance, this removes manual approval tracking overhead.

Archival rules automatically move completed PRDs to the archive/ subdirectory based on status completion. This keeps active documentation clean while maintaining historical records for reference.