SkillAgentSearch skills...

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 / Use

npx skills add product-on-purpose/pm-skills --skill iterate-retrospective

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Supported Platforms

Universal

Our assessment of iterate-retrospective

iterate-retrospective scores 81/100 on our quality scale, 996th of 1,148 Content & Media skills we index.

Its SKILL.md is 5.1 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.

It has 697 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so iterate-retrospective is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

iterate-retrospective compared with similar skills

All 4 of these similar skills score higher than iterate-retrospective; compare them before choosing.

SkillScoreStarsUpdatedFormat
iterate-retrospective (this skill)by product-on-purpose816972mo agoSKILL.md
taste-skillby Leonxlnx100118.3k10d agoCLAUDE.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.1k9d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server

Frequently asked questions

How do I install iterate-retrospective?
Run npx skills add product-on-purpose/pm-skills --skill iterate-retrospective. The install tabs above show the steps for each supported agent.
Which AI agents does iterate-retrospective work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is iterate-retrospective safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is iterate-retrospective still maintained?
The repository was last updated about 2 months ago, so iterate-retrospective is actively maintained.

name: iterate-retrospective description: 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. license: Apache-2.0 metadata: phase: iterate version: "2.2.0" updated: 2026-06-10 category: reflection frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose

<!-- 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 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 Select a retrospective format that fits the team's needs. Common options include:

    • Start/Stop/Continue: Simple and direct
    • 4Ls: Liked, Learned, Lacked, Longed for
    • Mad/Sad/Glad: Emotion-focused
    • Sailboat: Visual metaphor (wind=helps, anchor=holds back)
  3. Gather Input Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.

  4. Discuss and Prioritize Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.

  5. Define Action Items Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like "communicate better."

  6. Review Previous Actions Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.

  7. Document for Future Reference Capture the key points so they're available for future team members and for tracking patterns over time.

Project Memory Contract

Active only when .claude/pm-skills.local.md exists. With no file, ignore this section entirely and behave exactly as described above.

  • Reads: the recent artifacts[] entries, so the retrospective can look at what the cycle actually produced instead of relying on recall.
  • Writes: the lessons as an interpretation artifact.
  • Posture: propose the entry and wait for confirmation before writing, unless memory_auto_append: true is set, in which case append and echo what was written.
  • Write discipline: re-read the file immediately before writing, never from the copy that produced the proposal. If it changed in between, merge your entry into the current state and re-propose rather than overwriting; add only your own entry and leave every other field and section byte-identical. Nothing enforces this at runtime and the file is gitignored, so a careless whole-file write loses another session's work with no way to recover it.

A retrospective surfaces raw observations, patterns, and commitments at once. Record the durable half, the lessons, under a single tag; a downstream reader needs to know how firmly to weight the entry, and a mixed tag tells it nothing.

Output Format

Use the template in references/TEMPLATE.md to structure the output. A complete retrospective fills every template section: Overview; Previous Retrospective Review; What Went Well; What to Improve; Discussion Notes; Action Items; Parking Lot; Metrics and Trends; Facilitator Notes; and Next Retrospective.

Quality Checklist

Before finalizing, verify:

  • [ ] All attendees had opportunity to contribute
  • [ ] Both positives and improvements are captured
  • [ ] Action items have owners and due dates
  • [ ] Previous retrospective actions are reviewed
  • [ ] A reader who missed the retro can tell what was decided and who owns each action from this document alone

Examples

See references/EXAMPLE.md for a completed example.

Related Skills

View on GitHub
GitHub Stars697
CategoryContent
Updated2mo ago
Forks88

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions