Scrum Master
borghei/Claude-Skills
Data-driven Scrum Master for sprint health scoring, Monte Carlo velocity forecasting, retrospective analysis, capacity planning, and Tuckman team coaching.
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items.
Install Iterate Retrospective
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills iterate-retrospective --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/iterate-retrospective .claude/skills/iterate-retrospective && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .claude/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospectiveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills iterate-retrospective --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/iterate-retrospective .agents/skills/iterate-retrospective && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .agents/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills iterate-retrospective --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/iterate-retrospective .cursor/skills/iterate-retrospective && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .cursor/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/iterate-retrospective--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills iterate-retrospective --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/iterate-retrospective .gemini/skills/iterate-retrospective && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .gemini/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills iterate-retrospectiveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/iterate-retrospective .github/skills/iterate-retrospective && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .github/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills iterate-retrospective --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/iterate-retrospective .opencode/skills/iterate-retrospective && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iterate-retrospective" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective into .opencode/skills/iterate-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iterate-retrospective", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
iterate-retrospective- GitHub stars
- 716
- Token cost
- ~1.3k tokens
- SKILL.md length
- 638 words
- Files
- 6 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items.
- Works in 7 steps: Set the Context → Choose a Format → Gather Input → …
- Tasks that involve Retrospectives
- SKILL.md covers When to Use, When NOT to Use, Instructions and Project Memory Contract, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Iterate Retrospective is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `HISTORY.md`, `evals/output-scenarios/sprint-42.md` and `evals/trigger-fixtures.json`).
It sits in Product & Project Management, covering Retrospectives and Project management. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Retrospectives
- Tasks that involve Project management
Example prompts
- “Use the iterate-retrospective skill to facilitate and documents a team retrospective capturing what went well, what to improve, and action items”
- “/iterate-retrospective”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Set the Context
- Choose a Format
- Gather Input
- Discuss and Prioritize
- Define Action Items
- Review Previous Actions
- Document for Future Reference
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Iterate Retrospective loads about 1.3k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 638 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 638 words, ~1,299 tokens.
Download SKILL.mdSave it as
.claude/skills/iterate-retrospective/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- 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
- metadata.version
- 2.2.0
- metadata.updated
- 2026-06-10
- metadata.category
- reflection
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.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:
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.
Show full SKILL.md (281 more words)Show less
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.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/iterate-retrospective of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/output-scenarios/sprint-42.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Iterate Retrospective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iterate Retrospective this skillproduct-on-purpose/pm-skills | 716 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Scrum Masterborghei/Claude-Skills | 891 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Agile Coachborghei/Claude-Skills | 891 | — | ~1.2k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Agile Coach
borghei/Claude-Skills
Expert agile coaching: framework selection, maturity assessment, retrospective facilitation, transformation roadmaps.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Related
Categories
Questions about Iterate Retrospective
What does Iterate Retrospective do?
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Iterate Retrospective is an agent skill from product-on-purpose/pm-skills. Facilitates and documents a team retrospective capturing what went well, what to improve, and action items.
When should I use Iterate Retrospective?
Iterate Retrospective fits situations like: tasks that involve Retrospectives; tasks that involve Project management.
How do I install Iterate Retrospective in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a claude-code`. Or copy the skill folder (skills/iterate-retrospective in product-on-purpose/pm-skills) into .claude/skills/iterate-retrospective in your project. Claude Code loads it when a task matches its description.
How do I install Iterate Retrospective in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a codex`. Or copy the skill folder (skills/iterate-retrospective in product-on-purpose/pm-skills) into .agents/skills/iterate-retrospective in your project. Codex loads it when a task matches its description.
Can I use Iterate Retrospective in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill iterate-retrospective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iterate-retrospective, .gemini/skills/iterate-retrospective, .github/skills/iterate-retrospective and .opencode/skills/iterate-retrospective in your project.
What does Iterate Retrospective need to run?
SKILL.md names no scripts, command-line tools or credentials: Iterate Retrospective is instructions for the agent only.
Does Iterate Retrospective access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Iterate Retrospective safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Iterate Retrospective use?
Iterate Retrospective is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Iterate Retrospective use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Iterate Retrospective?
Skills that share tags, products or a category with Iterate Retrospective: Scrum Master (borghei/Claude-Skills, 891 stars), Agile Coach (borghei/Claude-Skills, 891 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Weekly Engineering Retro (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iterate Retrospective?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.