Estimated time: 5-10 minutes
Difficulty: Easy
Reversible: Yes (instructions provided)
v0.3.0 introduces a simplified folder structure and refined workflows. This guide helps you migrate your existing PRDs.
- Folder structure simplified -
02-review/removed, others renumbered - Workflow separation -
/setup-prdand/code-prdhave distinct roles - Review behavior - No automatic file movement, user stays in control
cd your-project/
cp -r product/prds product/prds.backup# Rename folders to match new structure
mv product/prds/03-ready product/prds/02-ready
mv product/prds/04-in-progress product/prds/03-in-progress
mv product/prds/05-complete product/prds/04-complete
# Remove 02-review folder (if exists)
rm -rf product/prds/02-reviewWindows users (PowerShell):
Move-Item product\prds\03-ready product\prds\02-ready
Move-Item product\prds\04-in-progress product\prds\03-in-progress
Move-Item product\prds\05-complete product\prds\04-complete
Remove-Item product\prds\02-review -Recurse -Force -ErrorAction SilentlyContinuenpm update -g claude-prd-workflowVerify installation:
npm list -g claude-prd-workflow
# Should show: claude-prd-workflow@0.3.0If your PRDs reference folder names in metadata, update them:
# Find PRDs with old folder references
grep -r "03-ready\|04-in-progress\|05-complete" product/prds/
# Update them manually or with sed:
find product/prds -name "*.md" -exec sed -i 's/03-ready/02-ready/g; s/04-in-progress/03-in-progress/g; s/05-complete/04-complete/g' {} \;# List your PRDs with new structure
/list-prds
# Should show correct folder locations/create-prd "New Feature" # → 01-draft/
/review-prd PRD-007 # → Moves to 02-review/
/review-prd PRD-007 # → Approves, moves to 03-ready/
/code-prd PRD-007 # → Moves to 04-in-progress/, starts coding/create-prd "New Feature" # → 01-draft/
/review-prd PRD-007 # → Updates metadata ONLY (stays in draft)
/setup-prd PRD-007 # → Moves to 02-ready/, creates branch, assigns
/code-prd PRD-007 # → Moves to 03-in-progress/, starts codingKey differences:
/review-prdno longer moves files- New
/setup-prdcommand handles branch creation + assignment - Clearer separation between review → setup → implementation
- All PRD folders renamed correctly
- Plugin updated to v0.3.0 (
npm list -g) -
/list-prdsshows correct folder structure - Test
/create-prdcreates in01-draft/ - Test
/setup-prdmoves to02-ready/ - Test
/code-prdmoves to03-in-progress/ - Backup can be deleted (
rm -rf product/prds.backup)
If you need to revert to v2.8.0:
# Rename back to old structure
mv product/prds/02-ready product/prds/03-ready
mv product/prds/03-in-progress product/prds/04-in-progress
mv product/prds/04-complete product/prds/05-complete
# Recreate 02-review folder
mkdir -p product/prds/02-reviewnpm install -g claude-prd-workflow@legacyrm -rf product/prds
mv product/prds.backup product/prdsAfter migrating, try these new features:
/setup-prd PRD-007
# Automatically assigns to your GitHub username/code-prd PRD-007
# Shows: "✅ 12/45 tasks completed (27%)"Add to your PRD metadata:
**Depends On**:
- PRD-003: Database schema
- PRD-005: Auth systemThen /code-prd will warn if dependencies aren't complete.
No. You can stay on v2.8.0 by installing claude-prd-workflow@legacy. However, v0.3.0+ is actively developed and receives new features.
Move them to either 01-draft/ or 02-ready/ depending on their status:
- Not reviewed yet: →
01-draft/ - Reviewed and approved: →
02-ready/
No. Branch names are unaffected. The migration only renames local folders.
Not recommended. The plugin expects the new structure. Migrate all at once using the steps above.
Update folder references manually:
sed -i 's/03-ready/02-ready/g; s/04-in-progress/03-in-progress/g; s/05-complete/04-complete/g' product/WORK_PLAN.md- Issue tracker: https://github.com/Yassinello/claude-prd-workflow/issues
- Discussions: https://github.com/Yassinello/claude-prd-workflow/discussions
- Documentation: Check README.md for updated workflows
Maintained by: Yassine Hamou-Tahra
Last Updated: 2025-10-28
Plugin Version: v0.3.0