Iterate Retrospective
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill iterate-retrospectivegit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/iterate-retrospective ~/.claude/skills/iterate-retrospectivePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Retrospective A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through. ## When to Use - At the end of every sprint (for agile teams) - After completing a significant project or milestone - Following a major incident or outage - When team dynamics feel off and need addressing - At regular intervals (monthly, quarterly) even without specific triggers - When onboarding new team members to establish improvement culture ## When NOT to Use - You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it - You are scoring an OKR cycle at close -> use `measure-okr-grader` - The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision` - You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap` ## Instructions When asked to facilitate or document a retrospective, follow these steps: 1. **Set the Context** Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context. 2. **Choose a Format**
Details
- Skill name
iterate-retrospective- Repository
- product-on-purpose/pm-skills
- Path
skills/iterate-retrospective/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Iterate Retrospective skill do?
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.
How do I install the Iterate Retrospective skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Iterate Retrospective popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Hypothesis
819product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Tool Design Sprint Sketch
819product-on-purpose/pm-skills
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday morning after Monday's target moment is locked. Output is the lightning demo board, sketch assignments, and the cohort of independent sketches that become Wednesday's heat-map material.
Iterate Refinement Notes
819product-on-purpose/pm-skills
Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.
Tool Note and Vote
819product-on-purpose/pm-skills
Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable to Foundation Sprint, Design Sprint, and any participatory decision context.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.