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.
Analyses sprint delivery data and produces a structured retrospective brief.
Install Retro Analysis
$ npx skills add mohitagw15856/pm-claude-skills --skill retro-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills retro-analysis --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/retro-analysis .claude/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .claude/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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/retro-analysisType 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 retro-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills retro-analysis --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/retro-analysis .agents/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .agents/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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 retro-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills retro-analysis --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/retro-analysis .cursor/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .cursor/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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/retro-analysis--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 retro-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills retro-analysis --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/retro-analysis .gemini/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .gemini/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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 retro-analysisInstalls 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 retro-analysis -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/retro-analysis .github/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .github/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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 retro-analysis -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 retro-analysis --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/retro-analysis .opencode/skills/retro-analysis && 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-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/retro-analysis into .opencode/skills/retro-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro-analysis", 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-analysis- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 677 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyses sprint delivery data and produces a structured retrospective brief.
- Works in 6 steps: Calculate: completion rate, carry-over… → Identify patterns: which ticket types… → Note any process or communication… → …
- Asked to run a retrospective
- SKILL.md covers Required Inputs, Process, Output Structure and Deeper Materials, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Retro Analysis is an agent skill from mohitagw15856/pm-claude-skills. Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/root-cause-vs-symptom.md`, `references/worked-example.md` and `templates/retro-board.md`).
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 run a retrospective
- Analyse sprint data
- Prepare a retro brief
- Turn sprint metrics into discussion prompts
Example prompts
- “Use the retro-analysis skill to analyse sprint delivery data and produces a structured retrospective brief”
- “/retro-analysis”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Calculate: completion rate, carry-over rate, unplanned work percentage
- Identify patterns: which ticket types were most likely to carry over? Which caused blockers?
- Note any process or communication breakdowns visible in the data
- Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint
- Suggest 1 concrete experiment for the next sprint based on the biggest friction point
- Validate — Confirm each prompt is specific to this sprint (not a recycled generic prompt), and that the recommended experiment is concrete…
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
Retro Analysis loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 677 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). 677 words, ~1,346 tokens.
Download SKILL.mdSave it as
.claude/skills/retro-analysis/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- retro-analysis
- description
- Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.
Retrospective Analysis Skill
Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened.
Required Inputs
Ask the user for these if not provided:
- Sprint tickets: planned vs. completed
- Carry-over tickets and reasons (if known)
- Tickets reopened after closing (quality signal)
- Any incidents or unplanned work (scope creep signal)
- Sprint velocity vs. historical average (trend context)
Process
- Calculate: completion rate, carry-over rate, unplanned work percentage
- Identify patterns: which ticket types were most likely to carry over? Which caused blockers?
- Note any process or communication breakdowns visible in the data
- Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint
- Suggest 1 concrete experiment for the next sprint based on the biggest friction point
- Validate — Confirm each prompt is specific to this sprint (not a recycled generic prompt), and that the recommended experiment is concrete and measurable
Output Structure
Sprint [Number] Retrospective Brief
By the Numbers:
- Planned: [n] tickets | Completed: [n] | Carry-over: [n] | Completion rate: [%]
- Unplanned work: [n] tickets ([%] of capacity)
- Velocity: [points] vs. [average] average
What the Data Suggests: [2-3 observations grounded in the numbers above]
Discussion Prompts:
- Start: [specific prompt based on this sprint's data]
- Stop: [specific prompt based on this sprint's data]
- Continue: [specific prompt based on this sprint's data]
Suggested Experiment for Next Sprint: [One concrete, testable process change — with a specific success metric]
Deeper Materials
This skill ships with support files — use them when they are available:
references/root-cause-vs-symptom.md— Retros That Change Things: Root Causes vs Symptoms. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/retro-board.md— a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Show full SKILL.md (367 more words)Show less
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Data grounding | Numbers missing or wrong; observations are opinions with no traceable source | Core rates computed correctly, but observations only restate the numbers without pattern analysis (ticket types, historical comparison) | Every observation traces to a computed figure, carry-over is broken down by type/cause, and velocity is compared against the historical trend, not just the average |
| Blamelessness | Brief names or implies individuals/disciplines as the cause ("QA missed them") | Neutral wording, but framing still points at effort or diligence rather than systemic conditions | Failure modes are reframed as process/coverage/scheduling patterns the data actually supports — a defensive reader would find nothing aimed at them |
| Prompt specificity | Start/Stop/Continue are recycled generic categories ("communicate better") | Prompts reference this sprint but stay at category level — no numbers, no named behaviour | Each prompt is welded to this sprint's data, names one specific behaviour, and is phrased to open discussion rather than dictate the answer |
| Experiment quality | No experiment, or a multi-quarter initiative dressed as one | One concrete change, but success is unmeasurable or can't be evaluated at the next retro | One process change testable within a single sprint, with explicit success metrics and a stated cost-if-wrong, checkable at the next retro |
Quality Checks
- Each Start/Stop/Continue prompt names a specific behaviour, not a vague category
- The recommended experiment is testable in one sprint
- Carry-over analysis identifies the ticket type or cause, not just the count
- Data observations don't assign blame — they describe patterns
- Velocity trend is mentioned in context (is this a one-off or a pattern?)
Anti-Patterns
- Do not assign blame to individuals in the retrospective brief — observations must describe patterns, not people
- Do not produce Start/Stop/Continue prompts that are vague categories — each must name a specific behaviour
- Do not recommend an experiment that cannot be completed within one sprint — small, testable experiments only
- Do not treat carry-over tickets as a velocity problem without first identifying the root cause category
- Do not run the same retrospective format every sprint — vary the format to prevent engagement fatigue
Example Trigger Phrases
- "Run a retrospective."
- "Analyse sprint data."
- "Prepare a retro brief."
- "Turn sprint metrics into discussion prompts."
© 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
SKILL.md and 3 other files (references) in skills/retro-analysis of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/root-cause-vs-symptom.md
- references/worked-example.md
- templates/retro-board.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Retro Analysis 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 Analysis this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | 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 Retro Analysis
What does Retro Analysis do?
Analyses sprint delivery data and produces a structured retrospective brief. Retro Analysis is an agent skill from mohitagw15856/pm-claude-skills. Analyses sprint delivery data and produces a structured retrospective brief.
When should I use Retro Analysis?
Retro Analysis fits situations like: asked to run a retrospective; analyse sprint data; prepare a retro brief; turn sprint metrics into discussion prompts.
How do I install Retro Analysis in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill retro-analysis -a claude-code`. Or copy the skill folder (skills/retro-analysis in mohitagw15856/pm-claude-skills) into .claude/skills/retro-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Retro Analysis in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill retro-analysis -a codex`. Or copy the skill folder (skills/retro-analysis in mohitagw15856/pm-claude-skills) into .agents/skills/retro-analysis in your project. Codex loads it when a task matches its description.
Can I use Retro Analysis 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 retro-analysis -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-analysis, .gemini/skills/retro-analysis, .github/skills/retro-analysis and .opencode/skills/retro-analysis in your project.
What does Retro Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Retro Analysis is instructions for the agent only.
Does Retro Analysis 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 Analysis 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 Analysis use?
Retro Analysis 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 Analysis use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 2k tokens, read only when the agent opens those files.
What are the alternatives to Retro Analysis?
Skills that share tags, products or a category with Retro Analysis: 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 Retro Analysis?
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.