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.
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.
Install Retro
$ npx skills add phuryn/pm-skills --skill retro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install phuryn/pm-skills retro --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/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-execution/skills/retro .claude/skills/retro && 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 "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .claude/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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/phuryn/pm-skills/tree/main/pm-execution/skills/retroType 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 phuryn/pm-skills --skill retro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install phuryn/pm-skills retro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pm-execution/skills/retro .agents/skills/retro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .agents/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 phuryn/pm-skills --skill retro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install phuryn/pm-skills retro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pm-execution/skills/retro .cursor/skills/retro && 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 "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .cursor/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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/phuryn/pm-skills.git --path pm-execution/skills/retro--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 phuryn/pm-skills --skill retro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install phuryn/pm-skills retro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pm-execution/skills/retro .gemini/skills/retro && 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 "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .gemini/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 phuryn/pm-skills retroInstalls 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 phuryn/pm-skills --skill retro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pm-execution/skills/retro .github/skills/retro && 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 "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .github/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 phuryn/pm-skills --skill retro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install phuryn/pm-skills retro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pm-execution/skills/retro .opencode/skills/retro && 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 "retro" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro into .opencode/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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
retro- GitHub stars
- 27k
- Token cost
- ~697 tokens
- SKILL.md length
- 269 words
- Files
- 1
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.
- Works in 5 steps: Choose a retro format based on context… → If the user provides raw feedback (e.g.,… → Analyze the sprint performance → …
- Running a retrospective
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Reflecting on a sprint
What it does
Retro is an agent skill from phuryn/pm-skills. Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Its SKILL.md is about 700 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: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.
When your agent uses it
- Running a retrospective
- Reflecting on a sprint
- Creating action items from team feedback
- Learning how to run effective retros
Example prompts
- “/retro”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Choose a retro format based on context (or let the user pick)
- If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages)
- Analyze the sprint performance
- Generate prioritized action items
- Create the retro summary
What it can do on your machine
Read from SKILL.md and the folder at commit 8607e3b. 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
Retro loads about 697 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 269 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 phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 269 words, ~697 tokens.
Download SKILL.mdSave it as
.claude/skills/retro/SKILL.md (or your agent's skills folder).- name
- retro
- description
- Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Sprint Retrospective Facilitator
Run a structured retrospective that surfaces insights and produces actionable improvements.
Context
You are facilitating a retrospective for $ARGUMENTS.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
Instructions
Choose a retro format based on context (or let the user pick):
Format A — Start / Stop / Continue:
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well that we should keep?
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
- Liked: What did the team enjoy?
- Learned: What new knowledge was gained?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Format C — Sailboat:
- Wind (propels us): What's driving us forward?
- Anchor (holds us back): What's slowing us down?
- Rocks (risks): What dangers lie ahead?
- Island (goal): Where are we trying to get to?
If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
- Group similar items into themes
- Identify the most frequently mentioned topics
- Note sentiment patterns (frustration, energy, confusion)
Analyze the sprint performance:
- Sprint goal: achieved or not?
- Velocity vs. commitment (over-committed? under-committed?)
- Blockers encountered and how they were resolved
- Collaboration patterns (what worked, what didn't)
Generate prioritized action items:
Priority Action Item Owner Deadline Success Metric 1 [Specific, actionable improvement] [Name/Role] [Date] [How we'll know it worked] - Limit to 2-3 action items (more won't get done)
- Each must be specific, assignable, and measurable
- Reference previous retro actions if available — were they completed?
Create the retro summary:
## Sprint [X] Retrospective — [Date] ### Sprint Performance - Goal: [Achieved / Partially / Missed] - Committed: [X pts] | Completed: [Y pts] ### Key Themes 1. [Theme] — [summary] ### Action Items 1. [Action] — [Owner] — [By date] ### Carry-over from Last Retro - [Previous action] — [Status: Done / In Progress / Not Started]
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
© phuryn, 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 pm-execution/skills/retro of phuryn/pm-skills.
Open the folder on GitHubat commit 8607e3b
Compare with similar skills
Retro 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 |
|---|---|---|---|---|---|---|
| Retro this skillphuryn/pm-skills | 27k | — | ~697 | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.6k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 350 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.6k | — | ~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 phuryn/pm-skills
All 67 skills in this repoAgreement-Based Code Review
phuryn/pm-skills
Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.
A/B Test Analysis
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
Team OKR Brainstorm
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
Cohort Analysis and Retention Explorer
phuryn/pm-skills
Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.
Dummy Dataset Generator
phuryn/pm-skills
Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.
Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Related
Categories
Questions about Retro
What does Retro do?
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Retro is an agent skill from phuryn/pm-skills. Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.
When should I use Retro?
Retro fits situations like: running a retrospective; reflecting on a sprint; creating action items from team feedback; learning how to run effective retros.
How do I install Retro in Claude Code?
Run `npx skills add phuryn/pm-skills --skill retro -a claude-code`. Or copy the skill folder (pm-execution/skills/retro in phuryn/pm-skills) into .claude/skills/retro in your project. Claude Code loads it when a task matches its description.
How do I install Retro in Codex?
Run `npx skills add phuryn/pm-skills --skill retro -a codex`. Or copy the skill folder (pm-execution/skills/retro in phuryn/pm-skills) into .agents/skills/retro in your project. Codex loads it when a task matches its description.
Can I use Retro 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 phuryn/pm-skills --skill retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/retro, .gemini/skills/retro, .github/skills/retro and .opencode/skills/retro in your project.
What does Retro need to run?
SKILL.md names no scripts, command-line tools or credentials: Retro is instructions for the agent only.
Does Retro 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 Retro 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 Retro use?
Retro 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 Retro use?
About 697 tokens (SKILL.md is roughly 2.8k 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 Retro?
Skills that share tags, products or a category with Retro: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.6k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 350 stars) and Deck Retro (asheshgoplani/agent-deck, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Retro?
phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,845 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on September 14, 2026.
Source: phuryn/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.