How do I install the Prp Prd Update skill?

Run npx skillmds@latest add wirasm/prp-prd-update-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Prp Prd Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Prp Prd Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Prp Prd Update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Prp Prd Update?

Wirasm (@wirasm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Prp Prd Update by wirasm — Agent Skill

Name: Prp Prd Update
Author: Wirasm

Prp Prd Update

Maintains PRD implementation-phase status and artifact links. Always use when a PRP workflow records a planned, implemented, or merged phase in its source PRD, when the user asks to update PRD progress, or when the user invokes $prp-prd-update.

Wirasm Updated Sep 21, 2026

File contents

Arguments: $ARGUMENTS (and $1, $2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.

Update PRD Phase

Maintain one source PRD's implementation lifecycle without changing its requirements or product decisions.

Arguments: $ARGUMENTS

Resolve and verify

Require an explicit stage, PRD path, and phase number. Read the entire PRD and select the phase by its exact number, never by a fuzzy title match. Stop if the phase is missing, duplicated, or the requested transition conflicts with recorded state.

The Implementation Phases table must have Plan, Report, and PR columns. When reading an older PRD, rename PRP Plan to Plan and add missing columns without losing any row data or changing unrelated content.

Apply the stage

planned — require the plan file to exist. Set Status to in-progress and record its absolute path in Plan.
implemented — require the plan and report files to exist and verify that the PR URL identifies an open or merged PR for the current repository. Keep Status as in-progress and record the absolute plan path, absolute report path, and PR URL.
merged — verify through GitHub that the recorded or supplied PR is merged. Set Status to complete and preserve all artifact links.

Never mark a phase complete merely because implementation passed or a PR exists. Never move status backward, replace a conflicting artifact silently, infer a phase number, or modify another phase. Repeating the same valid update must be harmless.

Verify and report

Re-read the exact phase row after editing. Confirm its status and links match the requested stage and that the Markdown table remains valid. Return the PRD path, phase number, resulting status, and recorded links. Do not create a separate report artifact.

---name: prp-prd-update-2description: Maintains PRD implementation-phase status and artifact links. Always use when a PRP workflow records a planned, implemented, or merged phase in its source PRD, when the user asks to update PRD progress, or when the user invokes $prp-prd-update.---> **Arguments:** `$ARGUMENTS` (and `$1`, `$2`, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.# Update PRD PhaseMaintain one source PRD's implementation lifecycle without changing its requirements or product decisions.**Arguments:** $ARGUMENTS## Resolve and verifyRequire an explicit stage, PRD path, and phase number. Read the entire PRD and select the phase by its exact number, never by a fuzzy title match. Stop if the phase is missing, duplicated, or the requested transition conflicts with recorded state.The Implementation Phases table must have `Plan`, `Report`, and `PR` columns. When reading an older PRD, rename `PRP Plan` to `Plan` and add missing columns without losing any row data or changing unrelated content.## Apply the stage- `planned` — require the plan file to exist. Set `Status` to `in-progress` and record its absolute path in `Plan`.- `implemented` — require the plan and report files to exist and verify that the PR URL identifies an open or merged PR for the current repository. Keep `Status` as `in-progress` and record the absolute plan path, absolute report path, and PR URL.- `merged` — verify through GitHub that the recorded or supplied PR is merged. Set `Status` to `complete` and preserve all artifact links.Never mark a phase complete merely because implementation passed or a PR exists. Never move status backward, replace a conflicting artifact silently, infer a phase number, or modify another phase. Repeating the same valid update must be harmless.## Verify and reportRe-read the exact phase row after editing. Confirm its status and links match the requested stage and that the Markdown table remains valid. Return the PRD path, phase number, resulting status, and recorded links. Do not create a separate report artifact.

Frequently asked questions