How do I install the Sprint Retro skill?

Run npx skillmds@latest add fadil369/sprint-retro in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sprint Retro safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sprint Retro?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sprint Retro free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sprint Retro?

fadil369 (@fadil369) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sprint Retro by fadil369 — Agent Skill

Name: Sprint Retro
Author: fadil369

File contents

Sprint Retro Facilitator

Automate sprint retrospective prep. Given a just-closed sprint, pull data from Linear and Slack, synthesize themes, and produce a ready-to-use retro doc before the meeting starts.

How to invoke

Provide:

Sprint name or ID in Linear (e.g. "Sprint 42" or a Linear cycle ID)
Slack channel to scan for sentiment (e.g. #eng-team)
Output destination: Notion page URL, or omit for inline output

Process

1. Pull sprint data from Linear

All issues in the closed sprint: title, assignee, status (shipped / slipped / re-scoped)
Cycle time per ticket (created → closed)
Any tickets re-scoped, re-assigned, or added mid-sprint
Blocked issues and their blockers

2. Scrape team Slack for sentiment signals

Threads containing: "blocked", "surprised", "waiting", "unclear", "LGTM", "nice", "shipped"
Messages with 🎉 🚀 ✅ reactions (positive signals)
Messages with 😬 🤔 ❓ reactions or :thread: chains > 10 replies (friction signals)
Link each signal back to the relevant ticket where possible

3. Write the retro doc

Three sections, 3–5 bullets each, every bullet backed by a specific ticket or message link:

Went well What shipped cleanly, what the team did well, positive patterns worth repeating.

Dragged What slowed the sprint down. Be specific — not "communication was bad" but "three tickets were re-assigned mid-sprint without Slack heads-up (LIN-123, LIN-456, LIN-789)".

Try next sprint Concrete, testable process changes. One sentence per bullet, actionable next Monday.

4. Propose one process change

End with a single recommended process change for next sprint and a rough confidence score (0–100%) that it will stick, with a one-line justification.

Output format

# Sprint Retro: [Sprint Name]
*Prepared: YYYY-MM-DD | [N] issues shipped | [N] slipped*

## Went well
- [Specific observation] → [LIN-XXX](link) / [Slack thread](link)
...

## Dragged
- [Specific friction point] → [LIN-XXX](link) / [Slack thread](link)
...

## Try next sprint
- [Actionable process change]
...

## Recommended change for next sprint
**[Change]** — Confidence: XX% — [One-line rationale]

Requirements

Linear MCP required to pull sprint data. Configure at https://mcp.linear.app/mcp.
Slack MCP required for sentiment scraping. Configure at https://mcp.slack.com/mcp.
Without MCP access, provide the sprint data manually and the agent will synthesize from text input.

---name: sprint-retrodescription: Pulls a closed sprint from Linear, synthesizes themes, and writes the retro doc before the meeting.---# Sprint Retro FacilitatorAutomate sprint retrospective prep. Given a just-closed sprint, pull data from Linear and Slack, synthesize themes, and produce a ready-to-use retro doc before the meeting starts.## How to invokeProvide:- **Sprint name or ID** in Linear (e.g. "Sprint 42" or a Linear cycle ID)- **Slack channel** to scan for sentiment (e.g. `#eng-team`)- **Output destination**: Notion page URL, or omit for inline output## Process### 1. Pull sprint data from Linear- All issues in the closed sprint: title, assignee, status (shipped / slipped / re-scoped)- Cycle time per ticket (created → closed)- Any tickets re-scoped, re-assigned, or added mid-sprint- Blocked issues and their blockers### 2. Scrape team Slack for sentiment signals- Threads containing: "blocked", "surprised", "waiting", "unclear", "LGTM", "nice", "shipped"- Messages with 🎉 🚀 ✅ reactions (positive signals)- Messages with 😬 🤔 ❓ reactions or :thread: chains > 10 replies (friction signals)- Link each signal back to the relevant ticket where possible### 3. Write the retro docThree sections, 3–5 bullets each, every bullet backed by a specific ticket or message link:**Went well**What shipped cleanly, what the team did well, positive patterns worth repeating.**Dragged**What slowed the sprint down. Be specific — not "communication was bad" but "three tickets were re-assigned mid-sprint without Slack heads-up (LIN-123, LIN-456, LIN-789)".**Try next sprint**Concrete, testable process changes. One sentence per bullet, actionable next Monday.### 4. Propose one process changeEnd with a single recommended process change for next sprint and a rough confidence score (0–100%) that it will stick, with a one-line justification.## Output format```# Sprint Retro: [Sprint Name]*Prepared: YYYY-MM-DD | [N] issues shipped | [N] slipped*## Went well- [Specific observation] → [LIN-XXX](link) / [Slack thread](link)...## Dragged- [Specific friction point] → [LIN-XXX](link) / [Slack thread](link)...## Try next sprint- [Actionable process change]...## Recommended change for next sprint**[Change]** — Confidence: XX% — [One-line rationale]```## Requirements- **Linear MCP** required to pull sprint data. Configure at `https://mcp.linear.app/mcp`.- **Slack MCP** required for sentiment scraping. Configure at `https://mcp.slack.com/mcp`.- Without MCP access, provide the sprint data manually and the agent will synthesize from text input.

Frequently asked questions

Sprint Retro