retro

Closes project phases by computing throughput metrics from GitHub issues and writing retrospectives.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/mobiustripper42/jig --skill retro-mobiustripper42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/mobiustripper42/jig/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/mobiustripper42/jig --skill retro-mobiustripper42

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a phase-end retrospective for a GitHub-based project?

Invoke the retro skill after completing a phase's work. It identifies the current phase from open issue labels, accounts for every issue, computes throughput from closedAt dates and points labels, updates PROJECT_PLAN.md, and appends a structured entry to RETROSPECTIVES.md.

How is phase velocity calculated from GitHub issues?

Throughput equals total points from closed issues' points:N labels divided by the phase span in calendar weeks, measured from first issue createdAt to last closedAt. Phases spanning under 7 days are recorded as bursts instead of a per-week rate.

Does the retro skill read session transcripts for time tracking?

No. The transcript-based active-time model is retired. All velocity data comes from GitHub issue dates and points labels; session files are read-only references and wall_clock appears only as an on-screen gut-check elsewhere.

When does the retro skill bump the project version?

Version bumps run only when package.json contains a version field. Deploy-off-main projects get a patch bump per merged PR plus a minor bump at phase close; projects with a production branch skip per-PR patches and only get the minor bump.

What happens to open issues when a phase closes?

Each open issue is handled interactively: move it to the next phase by swapping its phase label, leave it open and record it in the retro, or close it as not planned with an explanatory comment.