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.
SkillScore73Maintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 16 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill73%
Checks it passed that the model alone missed
The lessons must be recorded as an interpretation artifact type.
The response identifies memory_auto_append set to true as the required configuration.
The response advises using an OKR grading process rather than a retrospective structure.
and 2 more in the full report
5 fixed11 passed either way5 still failing1 broke
Pass-rate lift
+18 pp
Tokens
+38%
Agent turns
0%
Response time
-33%
Model gemini-3.6-flashMeasured 8/18/2026v216 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We want retrospective artifacts to append automatically to `.claude/pm-skills.local.md` without requiring explicit user confirmation on every write. What exact metadata key and value must be set in `.claude/pm-skills.local.md` to enable this behavior?
What was checked, without and with the skill
Checked
Without skill
With skill
The response identifies memory_auto_append set to true as the required configuration.
Missed
Passed
case-10 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md83 lines3 files
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:
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.
Choose a Format
Select a retrospective format that fits the team's needs. Common options include:
Gather Input
Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.
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.