What problem does it solve?
Keeping a Product Requirements Document in sync with actual implementation progress is error-prone: phases get marked complete prematurely, plan and report links go stale, and PR status is tracked by hand. This Skill maintains one source PRD's implementation lifecycle with strict, verifiable transitions.
Core Features & Use Cases
- Stage-based transitions: Records
planned, implemented, or merged states for a specific phase, requiring the plan file, report file, or verified GitHub PR as evidence for each stage.
- Table schema migration: Renames legacy
PRP Plan columns to Plan and adds missing Report and PR columns without losing row data or altering unrelated content.
- Guardrails against bad state: Refuses fuzzy phase matching, backward status moves, silent artifact replacement, and marking phases complete without a merged PR.
- Use Case: After merging the pull request for phase 3 of a feature, run the update to verify the PR is merged on GitHub, set the phase status to
complete, and preserve its plan and report links.
Quick Start
Ask the assistant to run /prp-prd-update with merged, the path to your PRD, and the phase number to mark that phase complete after verifying its PR.