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.
Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session.
Install Sprint Retro Facilitator
$ npx skills add mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sprint-retro-facilitator --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sprint-retro-facilitator .claude/skills/sprint-retro-facilitator && 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 "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .claude/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitatorType 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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sprint-retro-facilitator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sprint-retro-facilitator .agents/skills/sprint-retro-facilitator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .agents/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sprint-retro-facilitator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sprint-retro-facilitator .cursor/skills/sprint-retro-facilitator && 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 "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .cursor/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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/mohitagw15856/pm-claude-skills.git --path skills/sprint-retro-facilitator--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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sprint-retro-facilitator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sprint-retro-facilitator .gemini/skills/sprint-retro-facilitator && 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 "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .gemini/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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 mohitagw15856/pm-claude-skills sprint-retro-facilitatorInstalls 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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sprint-retro-facilitator .github/skills/sprint-retro-facilitator && 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 "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .github/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sprint-retro-facilitator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sprint-retro-facilitator .opencode/skills/sprint-retro-facilitator && 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 "sprint-retro-facilitator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sprint-retro-facilitator into .opencode/skills/sprint-retro-facilitator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro-facilitator", 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
sprint-retro-facilitator- GitHub stars
- 1.4k
- Token cost
- ~973 tokens
- SKILL.md length
- 482 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session.
- Works in 5 steps: Start from evidence. Themes come from… → Separate systemic from one-off. A… → Few actions, owned. 2–4 max, each with a… → …
- Asked to facilitate a retro
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: A Retro That… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sprint Retro Facilitator is an agent skill from mohitagw15856/pm-claude-skills. Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session. Use when asked to facilitate a retro, run a sprint retrospective, prep retro themes, or turn our sprint into a retro. Produces the data-grounded themes (from done/WIP/blocked work and any flow metrics), a start/stop/continue, 2–4 owned action items with checks, and a follow-up on last retro's actions so retros stop repeating themselves.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to facilitate a retro
- Run a sprint retrospective
- Prep retro themes
- Turn our sprint into a retro
Example prompts
- “/sprint-retro-facilitator”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Start from evidence. Themes come from the actual work — carried-over tickets, recurring blockers, a spike in cycle time — so the…
- Separate systemic from one-off. A blocker that hit three sprints running is a process theme; a freak incident isn't.
- Few actions, owned. 2–4 max, each with a name and a success check. A retro with 9 actions changes nothing.
- Close the last loop first. Review previous actions before generating new ones — accountability is what makes retros work.
- Blameless. Findings are about the system, not people; "the deploy process let a bad config through," not "X broke prod."
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Sprint Retro Facilitator loads about 973 tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 482 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 482 words, ~973 tokens.
Download SKILL.mdSave it as
.claude/skills/sprint-retro-facilitator/SKILL.md (or your agent's skills folder).- name
- sprint-retro-facilitator
- description
- Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session. Use when asked to facilitate a retro, run a sprint retrospective, prep retro themes, or turn our sprint into a retro. Produces the data-grounded themes (from done/WIP/blocked work and any flow metrics), a start/stop/continue, 2–4 owned action items with checks, and a follow-up on last retro's actions so retros stop repeating themselves.
Sprint Retro Facilitator
Retros fail two ways: they become a feelings-dump with no actions, or they generate actions no one owns and nothing changes — so next sprint has the same complaints. This grounds the retro in what actually happened (the tickets, the blockers, the metrics), pulls themes from evidence rather than the loudest voice, and produces a small number of owned actions — then holds last retro's actions accountable so the loop actually closes.
What This Skill Produces
- Evidence-grounded themes — patterns drawn from the sprint's done/WIP/blocked work and flow signals, not vibes
- Start / Stop / Continue — concrete, tied to the themes
- 2–4 action items — each with an owner and a "how we'll know it worked" check (fewer, real ones beat a long list)
- Last retro's follow-up — did the previous actions happen, and did they help?
Required Inputs
Ask for these if not provided:
- The sprint data — completed vs planned, tickets that were blocked/carried over, any incidents
- Flow signals (optional) — cycle time, throughput, WIP aging if you track them
- Team sentiment — anything the team already raised (or run it as prompts to gather)
- Last retro's actions — so we can check them (a retro that ignores its own history repeats it)
Framework: A Retro That Changes Something
- Start from evidence. Themes come from the actual work — carried-over tickets, recurring blockers, a spike in cycle time — so the discussion isn't just who's loudest.
- Separate systemic from one-off. A blocker that hit three sprints running is a process theme; a freak incident isn't.
- Few actions, owned. 2–4 max, each with a name and a success check. A retro with 9 actions changes nothing.
- Close the last loop first. Review previous actions before generating new ones — accountability is what makes retros work.
- Blameless. Findings are about the system, not people; "the deploy process let a bad config through," not "X broke prod."
Show full SKILL.md (172 more words)Show less
Output Format
Retro — Sprint [n]
Since last retro: [previous actions → happened? helped?]
Themes (from the data)
- [theme] — evidence: [tickets/metric]. Systemic or one-off?
Start / Stop / Continue
- Start: … · Stop: … · Continue: …
Actions (owned)
| Action | Owner | How we'll know it worked | By |
|---|
Quality Checks
- Themes cite actual sprint evidence (tickets/metrics), not just opinions
- Systemic patterns are distinguished from one-offs
- Actions are 2–4, each with a named owner and a success check
- Last retro's actions are reviewed before new ones are set
- Framing is blameless — system and process, not individuals
Anti-Patterns
- A vent session with no actions — cathartic, useless.
- Nine action items with no owners — nothing changes.
- Ignoring last retro — guarantees the same issues recur.
- Blame — turns the retro into something people stop being honest in.
- Themes from the loudest voice instead of the data.
Example Trigger Phrases
- "Facilitate our sprint retro from these tickets and metrics."
- "Run a retrospective — here's what got done and what got blocked."
- "Prep retro themes and a start/stop/continue for sprint 14."
- "Help me run a retro that actually leads to change."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sprint-retro-facilitator of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Sprint Retro Facilitator 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 |
|---|---|---|---|---|---|---|
| Sprint Retro Facilitator this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~973 | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.5k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Deck Retro
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
Criticism Self Criticism
HughYau/qiushi-skill
批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Sprint Retro Facilitator
What does Sprint Retro Facilitator do?
Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session. Sprint Retro Facilitator is an agent skill from mohitagw15856/pm-claude-skills. Run a sprint retrospective that produces real change — themes from what actually happened, honest start/stop/continue, and owned action items, not a vent session.
When should I use Sprint Retro Facilitator?
Sprint Retro Facilitator fits situations like: asked to facilitate a retro; run a sprint retrospective; prep retro themes; turn our sprint into a retro.
How do I install Sprint Retro Facilitator in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a claude-code`. Or copy the skill folder (skills/sprint-retro-facilitator in mohitagw15856/pm-claude-skills) into .claude/skills/sprint-retro-facilitator in your project. Claude Code loads it when a task matches its description.
How do I install Sprint Retro Facilitator in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a codex`. Or copy the skill folder (skills/sprint-retro-facilitator in mohitagw15856/pm-claude-skills) into .agents/skills/sprint-retro-facilitator in your project. Codex loads it when a task matches its description.
Can I use Sprint Retro Facilitator 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 mohitagw15856/pm-claude-skills --skill sprint-retro-facilitator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sprint-retro-facilitator, .gemini/skills/sprint-retro-facilitator, .github/skills/sprint-retro-facilitator and .opencode/skills/sprint-retro-facilitator in your project.
What does Sprint Retro Facilitator need to run?
SKILL.md names no scripts, command-line tools or credentials: Sprint Retro Facilitator is instructions for the agent only.
Does Sprint Retro Facilitator 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 Sprint Retro Facilitator 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 Sprint Retro Facilitator use?
Sprint Retro Facilitator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sprint Retro Facilitator use?
About 973 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sprint Retro Facilitator?
Skills that share tags, products or a category with Sprint Retro Facilitator: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars) and Deck Retro (asheshgoplani/agent-deck, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sprint Retro Facilitator?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.