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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 805
- Forks
- 102
01 前言 Front Matter
- name
- iterate-retrospective
- license
- Apache-2.0
- metadata
- { "phase": "iterate", "author": "product-on-purpose", "updated": 1781049600000, "version": "2.2.0", "category": "reflection", "frameworks": [ "triple-diamond", "lean-startup", "design-thinking" ] }
- 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.
02 资源文件 5
- 参考文档evals/output-scenarios/sprint-42.md2.0 KB
- 参考文档evals/trigger-fixtures.json4.3 KB
- 参考文档HISTORY.md1.7 KB
- 参考文档references/EXAMPLE.md8.2 KB
- 参考文档references/TEMPLATE.md3.7 KB
03 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 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:
- 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)
-
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.
-
Define Action Items Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like "communicate better."
-
Review Previous Actions Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.
-
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
interpretationartifact. - Posture: propose the entry and wait for confirmation before writing, unless
memory_auto_append: trueis 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.
04 同仓库更多 Skills
utility-update-pm-skills
Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.
utility-slideshow-creator
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.
utility-pm-workflow-orchestrator
Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.
utility-pm-workflow-builder
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.
utility-pm-skill-validate
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.