Check and update PRD status through lifecycle
Updates PRD status through lifecycle stages and moves files to appropriate directories.
/plugin marketplace add jpoutrin/product-forge/plugin install product-design@product-forge-marketplace<prd-file> [--set <status>]Category: Product & Strategy
prd-status <prd-file> <new-status> [--comment "reason for change"]
<prd-file>: Required - Path to the PRD file to update<new-status>: Required - New status (draft, review, approved, active, complete, archived)--comment: Optional - Comment explaining the status changeWhen this command is run, Claude Code should:
status field to new statuslast_updated to current dateapproved_by name and set approved_dateValid transitions:
status: APPROVED
approved_by: [Prompt for name]
approved_date: 2025-01-06
status: ARCHIVED
archive_date: 2025-01-06
archive_reason: [Use --comment or prompt]
final_task_completion: [Calculate if task file exists]
Add or update in PRD:
## Status History
- 2025-01-06: DRAFT → REVIEW (Ready for stakeholder feedback)
- 2025-01-07: REVIEW → APPROVED (Approved by Jane Smith)
- 2025-01-08: APPROVED → ACTIVE (Development started)
📝 Updating PRD Status...
Current Status: REVIEW
New Status: APPROVED
✅ Metadata updated:
- status: APPROVED
- approved_by: Jane Smith
- approved_date: 2025-01-06
- last_updated: 2025-01-06
📄 Moving file:
From: ./feature-auth-frd.md
To: product-docs/prds/approved/feature-auth-frd.md
✅ Status change complete!
Comment: "All stakeholders have reviewed and approved the requirements"
# Move PRD to review status
prd-status feature-auth-frd.md review --comment "Ready for stakeholder review"
# Approve a PRD (will prompt for approver name)
prd-status feature-auth-frd.md approved
# Archive a completed PRD
prd-status old-feature-frd.md archived --comment "Feature deprecated in v2.0"
# Mark PRD as active development
prd-status feature-auth-frd.md active