From rp1-dev
Audits PRD blueprints against implementation evidence in archives, features directories, and codebase. Classifies phases as Complete/Partial/Not Started and guides disposition decisions like archive, add/remove scope, defer, or continue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rp1-dev:blueprint-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Audits PRD documents against implementation evidence, identifies stale or completed blueprints, and guides disposition decisions (archive, modify scope, defer).
Audits PRD documents against implementation evidence, identifies stale or completed blueprints, and guides disposition decisions (archive, modify scope, defer).
Extract these parameters from the user's input:
| Parameter | Required | Default | Description |
|---|---|---|---|
PRD_NAME | Yes | - | PRD filename without extension |
/rp1-dev:blueprint-audit <prd-name>
{% dispatch_agent "rp1-dev:blueprint-auditor" %} MODE: audit PRD_NAME: {PRD_NAME} {% enddispatch_agent %}
Error Response:
{"type":"error","message":"...","available_prds":["..."]}
Output error message with available PRDs, then STOP.
Needs User Input (audit complete):
{"type":"needs_user_input","question":"relevance","phases":[...],"summary":{...}}
Display the audit table from agent output, then continue to Step 3.
{% ask_user "Is this PRD still relevant to your work?", options: "Archive", "Add scope", "Remove scope", "Continue", "Defer" %}
"Archive":
needs_user_input with question="closure_status"Question: "What is the closure status?"
Options:
- "Complete" - All planned work finished
- "Partial" - Some work deferred or abandoned
"Add scope":
"Remove scope":
"Continue":
"Defer":
Display agent's final output. Include:
npx claudepluginhub rp1-run/rp1Retroactively generates Blueprint PRDs, ADRs, and PRPs from git history, codebase structure, and existing docs for onboarding established projects.
Manages PRD lifecycle: applies naming conventions, maintains directory structure, enforces status transitions, links PRDs to tasks, runs quality checks, and automates archiving.
Audits and reorganizes PRDs, user stories, design docs, and project structure to eliminate stale or misleading context. Use when documentation drift, traceability gaps, or PRD cleanup is needed.