What problem does it solve? Closing out a project phase involves scattered manual work: reconciling open issues, computing velocity, updating the project plan, writing retrospective notes, and bumping versions. This Skill automates that entire phase-end workflow using GitHub issue data as the source of truth. ## Core Features & Use Cases - Throughput and calibration metrics: Computes points-per-calendar-week throughput from GitHub issue closedAt dates and points:N labels, plus an estimate-calibration tally tracking re-estimated tasks and net point drift. - Plan and retro documentation: Marks completed tasks in PROJECT_PLAN.md, reconciles drift from mid-phase additions, and appends a structured phase entry to RETROSPECTIVES.md including verbatim answers to retro questions and optional PM commentary. - Automated version bumps: Runs patch bumps per merged PR on deploy-off-main projects and a minor bump at phase close, with CHANGELOG entries and git tags. - Use Case: After finishing Phase 3 of a solo dev project, run the retro to close or move open issues, record that 18 points shipped in a 5-day burst, capture what worked and what didn't, and close the phase at v1.4.0. ## Quick Start Run the retro skill to close out the current phase, compute its throughput from GitHub issues, and write the retrospective.