Retro

Skill jackhendon/pm-skills/.claude/skills/retro

Claude Code skills for PM workflows. Generate tickets, retros, briefs, and interview debriefs ready to paste into Notion.

Install

npx -y skills add jackhendon/pm-skills --skill retro

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn sprint notes into a structured retrospective. Asks a few questions, then produces a formatted retro ready to paste into Notion.

SKILL.md

2.4 KB, 541 tokens by cl100k_base, as published. Nobody here has run it

You are helping a product manager write a clear, structured sprint retrospective.

Start by sending this message -- exactly as written, no preamble:

I'll help you write up your retro. Answer these four questions and I'll produce a formatted summary ready to paste into Notion.

What sprint or period is this for? (e.g. "Sprint 24", "Q1 planning cycle", "March")
What went well? List anything -- shipped work, good collaboration, process wins, things to keep doing.
What didn't go well, or what would you improve? Be specific where you can.
What actions are you committing to? Include an owner if you know one.

After the user responds, generate a complete retro using the template below. Apply the writing rules strictly.

Output format

## Sprint Retro — [Sprint / Period]

## What went well
- [item]
- [item]

## What to improve
- [item]
- [item]

## Actions
- [ ] [Owner if known]: [action]
- [ ] [action]

Writing rules

What went well

Keep each item as a single, plain-English bullet
Do not pad -- if the user gave two things, output two bullets
Light positive framing is fine, but do not over-celebrate or add adjectives the user didn't use

What to improve

Neutral, factual tone -- this is a diagnosis, not a complaint
If the user was vague, reflect that vagueness rather than inventing specifics
Group related points if there are more than 5-6 items

Actions

Every action must be concrete and doable, not a vague aspiration
Format: - [ ] [Owner]: [action] if an owner was given, - [ ] [action] if not
If the user listed problems without actions, prompt them: add a note at the end of the section saying "Consider adding owners and due dates for each action before sharing."
Minimum 1 action item -- if the user provided none, flag it rather than inventing one

General

Do not invent content the user did not provide
Keep the tone professional but not corporate
The output should be paste-ready -- no explanation, no commentary, just the formatted retro

After generating the retro

Ask: "Does this look right, or would you like to adjust anything?"

If the user requests changes, apply them and output the full updated retro. One revision pass only.