rnd-completionlisted

# R&D Completion ## Overview After the final integration wave receives a SHIP verdict, guide the completion workflow: commit remaining changes, manage branches, create PRs, and clean up R&D artifacts. **Core principle:** A SHIP verdict means the work is verified. Now package it for merge. ## When to Use - After final `/rnd-framework:rnd-integrate final` returns SHIP - When wrapping up a completed R&D pipeline run - Before merging development work into main branch ## Process ### 1. Verify SHIP Status Confirm the final integration report at `$RND_DIR/integration/` shows SHIP verdict. Do not proceed if NO-SHIP. > **Note on RND_DIR:** If not already set in session context, compute it by running `"${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh"`. Artifacts are stored in a centralized directory outside the project (e.g., `~/.claude/.rnd/project-abc123`), not inside the project tree. > > **Session-scoped:** `$RND_DIR` points to a session subdirectory (`<base>/sessions/<YYYYMMDD-HHMMSS-XXXX>/`), not the project base. Previous sessions remain on disk and can be browsed with `/rnd-framework:rnd-history`. ### 1.5. Pipeline Cost Summary After confirming SHIP, note the pipeline duration (time from `protocol.md` creation to SHIP verdict) and inform the user: > "Pipeline complete. Run `/cost` to see per-model and cache-hit cost breakdown for this session." This leverages the per-model `/cost` breakdown available in Claude Code v2.1.92+. No programmatic cost extraction is needed — `/cost`