Retro
Scannednpx machina-cli add skill jackhendon/pm-skills/retro --openclawYou 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.
Source
git clone https://github.com/jackhendon/pm-skills/blob/main/.claude/skills/retro/SKILL.mdView on GitHub Overview
Turns sprint notes into a structured retrospective by prompting with four questions and generating a Notion-ready summary. It helps teams capture what went well, what didn’t, and concrete actions in a paste-friendly format.
How This Skill Works
Four prompts collect your sprint data, then the tool renders a complete retro using the defined template. The output is Notion-ready, pasteable markdown with sections for What went well, What to improve, and Actions.
When to Use It
- At sprint end to summarize outcomes for stakeholders
- When you want a consistent, Notion-ready retro format
- If you turn scattered notes into a structured recap
- For remote or distributed teams relying on shared docs
- When you need actionable items with owners (if known)
Quick Start
- Step 1: Answer the four questions about your sprint
- Step 2: Review the generated retro for Notion-ready formatting
- Step 3: Copy-paste the retro into Notion and make minor adjustments
Best Practices
- Ask four questions during the sprint to guide the recap
- Be specific in 'What went well' and 'What to improve'
- Keep tone neutral and diagnose issues, not vent
- Assign concrete owners to actions when possible
- Paste the output into Notion and adjust formatting if needed
Example Use Cases
- Sprint 23 recap focusing on feature delivery and process tweaks
- Remote team retro with Notion-friendly formatting
- Bug-fix sprint turned into implementable actions
- Maintenance sprint with clear ownership
- Cross-functional sprint aligning on collaboration improvements
