blueprint-auditlisted

# 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**: ```json {"type":"error","message":"...","available_prds":["..."]} ``` Output error message with available PRDs, then STOP. **Needs User Input** (audit complete): ```json {"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