Help us improve
Share bugs, ideas, or general feedback.
From product-design
Archives completed or cancelled PRD files to product-docs/prds/archive/YYYY/QX/ directories, adds YAML metadata (archive_date, reason, task completion %), moves linked tasks, uses git mv. Use post-implementation.
npx claudepluginhub jpoutrin/product-forge --plugin product-designHow this skill is triggered — by the user, by Claude, or both
Slash command
/product-design:prd-archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Category**: Product & Strategy
Archives completed PRD files from active to archives directory with associated features and closure summary. Confirms status, handles partial completion, and checks knowledge base staleness in RP1 workflows.
Archives completed PRDs and associated tasks/progress files to .plans/archive/. Parses task YAML to verify completion. Preview with --dry-run.
Manages PRD lifecycle: applies naming conventions, maintains directory structure, enforces status transitions, links PRDs to tasks, runs quality checks, and automates archiving.
Share bugs, ideas, or general feedback.
Category: Product & Strategy
prd-archive <prd-file> [--reason <reason>] [--force]
<prd-file>: Required - Path to the PRD file to archive--reason: Optional - Reason for archiving (default: "Implementation complete" or "Project cancelled")--force: Optional - Archive even if status is not COMPLETE or ARCHIVEDWhen this command is run, Claude Code should:
product-docs/prds/archive/YYYY/product-docs/prds/archive/YYYY/cancelled/Add to PRD header before moving:
status: ARCHIVED
archive_date: 2025-01-06
archive_reason: Implementation complete - v1.0 released
final_task_completion: 100%
implementation_duration: 15 days
original_location: product-docs/prds/active/feature-prds/
product-docs/prds/archive/
├── 2025/
│ ├── Q1/
│ │ ├── completed/
│ │ │ ├── user-auth-frd.md
│ │ │ └── user-auth-frd-tasks.md
│ │ ├── cancelled/
│ │ │ └── experimental-feature-frd.md
│ │ └── 2025-Q1-archive-summary.md
│ └── Q2/
└── 2024/
📦 Archiving PRD: user-authentication-frd.md
Current Status: COMPLETE
Task Completion: 100% (20/20 tasks)
✅ Adding archive metadata:
- archive_date: 2025-01-06
- archive_reason: Implementation complete - v1.0 released
- final_task_completion: 100%
- implementation_duration: 15 days
📁 Moving to archive:
From: product-docs/prds/active/feature-prds/user-authentication-frd.md
To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd.md
📄 Also archiving linked task file:
To: product-docs/prds/archive/2025/Q1/completed/user-authentication-frd-tasks.md
✅ Archive complete!
📊 Archive Summary:
- Implementation started: 2024-12-22
- Implementation completed: 2025-01-06
- Total duration: 15 days
- Final status: Successfully delivered
Create quarterly summary when archiving (e.g., 2025-Q1-archive-summary.md):
# Q1 2025 Archive Summary
## Completed PRDs (3)
1. **user-authentication-frd.md**
- Archived: 2025-01-06
- Duration: 15 days
- Completion: 100%
2. **search-enhancement-frd.md**
- Archived: 2025-02-15
- Duration: 22 days
- Completion: 100%
## Cancelled PRDs (1)
1. **experimental-ai-frd.md**
- Archived: 2025-01-20
- Reason: Project scope changed
- Completion at cancellation: 35%
## Statistics
- Total PRDs archived: 4
- Success rate: 75% (3/4)
- Average implementation time: 18.5 days
# Archive a completed PRD
prd-archive user-authentication-frd.md
# Archive with custom reason
prd-archive old-feature-frd.md --reason "Superseded by new design"
# Force archive of active PRD
prd-archive experimental-frd.md --force --reason "Project cancelled"
# Archive from different location
prd-archive ./drafts/completed-feature-frd.md