Agent skill · AI & Agents

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.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill iterate-retrospective --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 4 KB
Bundled scripts: none
Version: 2.1.0
Declared author: product-on-purpose
Path: skills/iterate-retrospective/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # 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 ask

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Instructions
  4. Output Format
  5. Quality Checklist
  6. Examples
Ships with 5 files
  • HISTORY.md
  • evals/output-scenarios/sprint-42.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
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 it?

Run `npx skills add product-on-purpose/pm-skills --skill iterate-retrospective --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going