forge-retrolisted

# forge-retro Close out a release cycle. Synthesize the cycle's history, blockers, lessons, and mined skill proposals into a single retrospective document the user can review, share, and act on for the next cycle. ## When to Use - User runs `/forge:retro` - Stage 12 (Release) gate has just passed - User says "retro", "retrospective", "post-mortem", "wrap up the cycle" - Before starting a new cycle, to lock in lessons and approve mined skills ## Pre-flight Confirm the project is at the right point: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py --cwd . read ``` If `pipeline/state.md` is missing, tell the user the project is not Forge-managed and suggest `/forge:init`. If `current_stage < 12`, warn that the cycle is not complete and ask whether to proceed early (acceptable for mid-cycle pulse checks). Refresh the skill-mining results so the retro shows the latest proposals: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/skill_miner_bg.py --forge-dir .forge --cwd . ``` ## Steps ### 1. Collect cycle inputs Read each of these in parallel — they all contribute to the retro: - `pipeline/state.md` — current stage, cycle, stage history, last reflection, blockers - `tasks/todo.md` — Archive section (completed tasks for this cycle) - `tasks/lessons.md` — lessons captured (filter to entries dated within this cycle) - `.forge/sessions/*.md` — session summaries written by `session-end.py` - Pending skill proposals: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scrip