What problem does it solve? After shipping significant implementation work, teams lose track of what changed, documentation drifts out of sync, reusable patterns go uncaptured, and tech debt accumulates silently. This Skill runs a structured retrospective that maps the blast radius, audits documentation accuracy, extracts reusable patterns, and inventories tech debt before that knowledge is lost. ## Core Features & Use Cases - Blast Radius Mapping: Builds a manifest of every package, app, and file created, modified, or deleted, grouped by package, using implementation plans, walkthroughs, and git diffs. - Documentation Audit: Checks READMEs, sidecar files, changelogs, and barrel exports against actual code, reporting findings by severity (MISLEADING, STALE, MISSING, ACCURATE) with cited evidence. - Pattern & Skill Extraction: Identifies reusable patterns with reuse-potential ratings and recommends creating or updating skills and knowledge items, checking the skill index first to avoid duplicates. - Use Case: After merging a large multi-package feature, run /retro to get a report covering what changed, which docs are now stale, what patterns deserve codification, difficulty analysis, and a prioritized tech debt inventory with follow-up actions. ## Quick Start Run /retro after completing a significant implementation to generate a full retrospective report of changes, documentation gaps, and follow-up work.
