prp-prd-update

Updates PRD implementation-phase status and artifact links in Markdown tables.

2.2k|608|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-prd-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-prd-update
Source: https://github.com/Wirasm/PRPs-agentic-eng/tree/main/plugins/prp-core/skills/prp-prd-update
Command: npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-prd-update

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about prp-prd-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update PRD implementation phase status?

Invoke the update with a stage (planned, implemented, or merged), the PRD path, and the exact phase number. The Skill edits the Implementation Phases table, setting Status and recording plan, report, and PR links as appropriate.

How do I mark a PRD phase as complete after merging a PR?

Use the merged stage with the PRD path and phase number. The Skill verifies through GitHub that the recorded or supplied PR is actually merged before setting Status to complete, preserving all existing artifact links.

Can a PRD phase be marked complete just because implementation passed?

No. The Skill never marks a phase complete merely because implementation passed or a PR exists. Completion requires the merged stage with GitHub verification that the pull request is actually merged.

What happens if my PRD uses the old PRP Plan column name?

When reading an older PRD, the Skill renames the PRP Plan column to Plan and adds any missing Report and PR columns. It preserves all existing row data and does not change unrelated content.

Why does the PRD update fail when I reference a phase by title?

The Skill selects phases only by exact number, never by fuzzy title matching. It stops if the phase is missing, duplicated, or the requested transition conflicts with the recorded state.

Is it safe to run the same PRD phase update twice?

Yes. Repeating the same valid update is harmless by design. The Skill never moves status backward, silently replaces conflicting artifacts, or modifies other phases.