blueprint-audit

blueprint-audit is a skill for Claude Code from rp1-run/rp1. It costs 18 tokens per session (751 once invoked), scanned A, original, Apache-2.0.

A workflow that compares a project requirements document with evidence from completed work, archived files, and the codebase. It then guides a decision about what to do with the plan.

In plain words
What is it for?
It helps audit a PRD, assess implementation progress, and decide whether to archive it, change its scope, or defer it.
Why use it?
It shows which planned phases are complete, partly complete, or not started, helping prevent outdated plans from directing current work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rp1-dev plugin — 23 skills, 36 agents shipped together

Good fit It helps audit a PRD, assess implementation progress, and decide whether to archive it, change its scope, or defer it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rp1-run/rp1/blueprint-audit
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add rp1-run/rp1 --skill blueprint-audit
Clone the repo
git clone --depth 1 https://github.com/rp1-run/rp1

Made for: Claude Code.

Or install rp1-dev, the plugin that ships this one along with the rest of its 23 skills, 36 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for blueprint-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/rp1-run/rp1/blueprint-audit/github.svg)](https://agentmods.dev/skills/rp1-run/rp1/blueprint-audit)
Your own site
<a href="https://agentmods.dev/skills/rp1-run/rp1/blueprint-audit"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/blueprint-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for blueprint-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/rp1-run/rp1/blueprint-audit"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/blueprint-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 751 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00751
Opus 5.5 $0.00007 $0.00300
Sonnet 5.5 $0.00004 $0.00150
Haiku 4.5 $0.00002 $0.00075

Measured 1mo ago against content hash 8e35833bbd06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blueprint-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dev/skills/blueprint-audit/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blueprint Audit

Audits PRD documents against implementation evidence, identifies stale or completed blueprints, and guides disposition decisions (archive, modify scope, defer).

Usage

/rp1-dev:blueprint-audit <prd-name>

Behavior

  • Extracts phases/milestones from PRD document
  • Checks archives and features directories for evidence
  • Searches codebase when archive/feature evidence insufficient
  • Classifies each phase as Complete/Partial/Not Started
  • Presents audit results with evidence summary
  • Guides user through disposition decision

Execution

Step 1: Run Audit

{% dispatch_agent "rp1-dev:blueprint-auditor" %} MODE: audit PRD_NAME: {PRD_NAME} KB_ROOT: {kbRoot} WORK_ROOT: {workRoot} {% enddispatch_agent %}

Step 2: Handle Audit Response

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.

Step 3: Ask Relevance Question

{% ask_user "Is this PRD still relevant to your work?", options: "Archive", "Add scope", "Remove scope", "Continue", "Defer" %}

Step 4: Handle User Choice

"Archive":

  1. Invoke agent with MODE=action, USER_CHOICE=archive
  2. Agent returns needs_user_input with question="closure_status"
  3. Ask user:
    Question: "What is the closure status?"
    Options:
    - "Complete" - All planned work finished
    - "Partial" - Some work deferred or abandoned
    
  4. If "Partial", ask for gap documentation (freeform text)
  5. Invoke agent with MODE=action, USER_CHOICE=archive_confirm, SCOPE_INPUT={status}|{gaps}

"Add scope":

  1. Ask user for new scope description (freeform text)
  2. Invoke agent with MODE=action, USER_CHOICE=add_scope, SCOPE_INPUT={description}

"Remove scope":

  1. Present list of Not Started/Partial phases from audit
  2. Ask user which phase IDs to remove (multi-select or comma-separated)
  3. Invoke agent with MODE=action, USER_CHOICE=remove_scope, SCOPE_INPUT={phase_ids}

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 108 lines · 18 tokens per session scan A 8e35833bbd06

Subscribe to this mod's changes

blueprint-audit is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 18 tokens to every session and 751 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

Related

Other skills, from other repositories

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".

intent-driven-dev/intent-driven-template · 61 tokens

openspec-bulk-apply-change

Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.

intent-driven-dev/intent-driven-template · 30 tokens

product-management

Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy. Use this skill for product planning, writing PRDs, defining MVPs, or competitive analysis.

HK-hub/AgentSkills · 50 tokens

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".

intent-driven-dev/intent-driven-template · 58 tokens

openspec-archive-change

Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".

intent-driven-dev/intent-driven-template · 50 tokens

prd-to-plan

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

HK-hub/AgentSkills · 61 tokens