blueprint-archivelisted

# PRD Archive Archives completed PRD docs from active -> archives dir with associated features. ## Usage ``` /rp1-dev:blueprint-archive <prd-name> ``` ## Behavior - Moves `.rp1/work/prds/<PRD_NAME>.md` -> `.rp1/work/archives/prds/<PRD_NAME>/prd.md` - Archives associated completed features to `.rp1/work/archives/features/` - Generates `closure_summary.md` with archive metadata - Checks KB staleness and suggests `/knowledge-build` if needed - Creates archive directories if missing ## Execution ### Step 1: Scan PRD {% dispatch_agent "rp1-dev:prd-archiver" %} MODE: scan PRD_NAME: {PRD_NAME} KB_ROOT: {kbRoot} WORK_ROOT: {workRoot} {% enddispatch_agent %} ### Step 2: Handle Scan Response Parse JSON response from agent. **Error Response** (`type: "error"`): ```json {"type":"error","message":"...","available_prds":["prd1","prd2"]} ``` Output error message with available PRDs list, then STOP. **Needs Confirmation** (`type: "needs_confirmation"`): ```json { "type": "needs_confirmation", "prd_name": "...", "prd_title": "...", "associated_features": [...], "message": "..." } ``` Continue to Step 3. ### Step 3: Confirm Closure Status {% ask_user "Archive PRD '{PRD_NAME}' ({prd_title})? {message}", options: "Yes - Objectives fully met", "Partial - Some objectives met", "No - Cancel" %} Handle response: - **"Yes"**: Go to Step 4 with `CLOSURE_STATUS=complete` - **"Partial"**: Go to Step 4a - **"No"**: Output `Archive aborted by user.` + STOP ### Step 4a: Document