← ClaudeAtlas

retrospectivelisted

Runs an epic retrospective that writes docs/epics/epic-N-retro-{date}.md, sweeps deferred items and security findings, syncs the PRD and architecture, updates CLAUDE.md conventions, and stamps the epic as retro-complete. Use when an epic is finished, or when the user says "retrospective", "retro", or "retro for epic N".
rterakedis/leanwheel-skills · ★ 2 · Testing & QA · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Retrospective Skill **Goal:** Extract learnings and update CLAUDE.md so next sprint starts smarter. **Role:** Ask questions and record answers (don't draw conclusions). ## Activation 1. Detect epic: user specifies (e.g. "retro for epic 2") or infer from most recent `Status: done` stories in `docs/epics/`. Ask if ambiguous. 2. Read `docs/epics/{epic_num}-*.md` with `Status: done` or `review`. Summarize shipped. 3. Read CLAUDE.md and the previous epic's retro doc (avoid duplication; check prior conventions held). 4. Present summary, then ask seven questions. ## Seven Questions **Always human-in-the-loop.** Ask the seven questions **one at a time and wait for each answer** — including when invoked from the `/epic-flywheel` boundary. Auto-generating the retro from git history (or any other artifact) is forbidden: the questions exist to capture the *user's* perspective, not to restate what the code already shows. 1. **What did we ship?** → Final list of shipped stories with one-line outcomes. 2. **What went well?** → Approaches that paid off — patterns to keep, not change. Distinct from Q4 (codifying); this is reinforcement. 3. **What slowed us down?** → Blockers and root causes. For each blocker, ask "why didn't we catch this earlier?" at least twice (5-whys-lite). 4. **What patterns emerged?** → Approaches/structures/decisions worth codifying. 5. **Did last sprint's conventions hold?** → Read the previous retro's "CLAUDE.md Conventions Added" section. Audit one or two s