retro-analysis
Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.
npx skills add mohitagw15856/pm-claude-skills --skill retro-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Retrospective Analysis Skill Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened. ## Required Inputs Ask the user for these if not provided: - **Sprint tickets: planned vs. completed** - **Carry-over tickets and reasons** (if known) - **Tickets reopened after closing** (quality signal) - **Any incidents or unplanned work** (scope creep signal) - **Sprint velocity vs. historical average** (trend context) ## Process 1. Calculate: completion rate, carry-over rate, unplanned work percentage 2. Identify patterns: which ticket types were most likely to carry over? Which caused blockers? 3. Note any process or communication breakdowns visible in the data 4. Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint 5. Suggest 1 concrete experiment for the next sprint based on the biggest friction point 6. **Validate** — Confirm each prompt is specific to this sprint (not a recycled generic prompt), and that the recommended experiment is concrete and measurable ## Output Structure ### Sprint [Number] Retrospective Brief **By the Numbers:** -
- Required Inputs
- Process
- Output Structure
- Sprint [Number] Retrospective Brief
- Deeper Materials
- Scoring Rubric (0–40)
- Quality Checks
- Anti-Patterns
What does the retro-analysis skill do?
Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill retro-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.