How do I install the Retro skill?

Run npx skillmds@latest add drn/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 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 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 Retro free to use?

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

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

Retro by drn — Agent Skill

Name: Retro
Author: drn

File contents

Retrospective

Structured retrospective for projects, sprints, or incidents. Captures learnings and optionally persists them to the knowledge base.

Arguments

$ARGUMENTS - Optional: --incident for post-incident template, or a topic/project name

Context

Recent commits: !git log --oneline -20 2>/dev/null | head -20
Merged PRs: !gh pr list --state merged --limit 10 2>/dev/null | head -10
Knowledge base: !cat context/knowledge/index.md 2>/dev/null | head -30
Current branch: !git branch --show-current

Instructions

Step 1: Choose template

IF --incident is in $ARGUMENTS, use the Incident template. OTHERWISE, use the Standard template.

Step 2: Gather context

Review the recent commits and merged PRs from the context above. Summarize the scope of work that this retro covers. If the user provided a topic, focus on that.

Step 3: Present and collaborate

Standard Template

## Retrospective: <topic or date>

### What Went Well
- <positive outcomes, wins, good patterns>

### What Did Not Go Well
- <pain points, friction, mistakes>

### Action Items
- [ ] <concrete next step with owner if applicable>

### Key Learnings
- <insights to carry forward>

Incident Template

## Post-Incident Review: <incident name>

### Timeline
| Time | Event |
|------|-------|
| | <what happened> |

### Impact
- **Users affected:**
- **Duration:**
- **Severity:**

### Root Cause
<what actually caused the issue>

### What Went Well
- <effective response actions>

### What Did Not Go Well
- <gaps in detection, response, or prevention>

### Action Items
- [ ] <concrete remediation with owner and deadline>

### Follow-ups
- [ ] <longer-term improvements>

Present the template pre-filled with whatever you can infer from the git context. Ask the user to fill in, correct, or expand each section. Iterate until the user is satisfied.

Step 4: Knowledge capture (optional)

IF a knowledge base exists (check context above for context/knowledge/index.md):

Propose adding key learnings as a new topic or updating an existing topic
Only add durable, reusable insights — not session-specific details
Follow the format in /knowledge (bold entity names, standalone facts, date-stamp volatile info)

IF no knowledge base exists, skip this step entirely. Do not suggest creating one.

Step 5: Save

Offer to:

Copy to clipboard
Save to .context/retros/<date>-<slug>.md
Both

---name: retrodescription: Run a structured retrospective or post-incident review with optional knowledge base capture. Use for running retrospectives, postmortems, or incident reviews.---# RetrospectiveStructured retrospective for projects, sprints, or incidents. Captures learnings and optionally persists them to the knowledge base.## Arguments- `$ARGUMENTS` - Optional: `--incident` for post-incident template, or a topic/project name## Context- Recent commits: !`git log --oneline -20 2>/dev/null | head -20`- Merged PRs: !`gh pr list --state merged --limit 10 2>/dev/null | head -10`- Knowledge base: !`cat context/knowledge/index.md 2>/dev/null | head -30`- Current branch: !`git branch --show-current`## Instructions### Step 1: Choose templateIF `--incident` is in `$ARGUMENTS`, use the **Incident template**.OTHERWISE, use the **Standard template**.### Step 2: Gather contextReview the recent commits and merged PRs from the context above. Summarize the scope of work that this retro covers. If the user provided a topic, focus on that.### Step 3: Present and collaborate#### Standard Template```markdown## Retrospective: <topic or date>### What Went Well- <positive outcomes, wins, good patterns>### What Did Not Go Well- <pain points, friction, mistakes>### Action Items- [ ] <concrete next step with owner if applicable>### Key Learnings- <insights to carry forward>```#### Incident Template```markdown## Post-Incident Review: <incident name>### Timeline| Time | Event ||------|-------|| | <what happened> |### Impact- **Users affected:**- **Duration:**- **Severity:**### Root Cause<what actually caused the issue>### What Went Well- <effective response actions>### What Did Not Go Well- <gaps in detection, response, or prevention>### Action Items- [ ] <concrete remediation with owner and deadline>### Follow-ups- [ ] <longer-term improvements>```Present the template pre-filled with whatever you can infer from the git context. Ask the user to fill in, correct, or expand each section. Iterate until the user is satisfied.### Step 4: Knowledge capture (optional)IF a knowledge base exists (check context above for `context/knowledge/index.md`):- Propose adding key learnings as a new topic or updating an existing topic- Only add durable, reusable insights — not session-specific details- Follow the format in `/knowledge` (bold entity names, standalone facts, date-stamp volatile info)IF no knowledge base exists, skip this step entirely. Do not suggest creating one.### Step 5: SaveOffer to:1. Copy to clipboard2. Save to `.context/retros/<date>-<slug>.md`3. Both

Frequently asked questions

Retro