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 close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path.
Install Engagement Retro
$ npx skills add mohitagw15856/pm-claude-skills --skill engagement-retro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engagement-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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engagement-retro .claude/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .claude/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-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 mohitagw15856/pm-claude-skills --skill engagement-retro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engagement-retro --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/engagement-retro .agents/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .agents/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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 mohitagw15856/pm-claude-skills --skill engagement-retro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engagement-retro --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/engagement-retro .cursor/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .cursor/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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/mohitagw15856/pm-claude-skills.git --path skills/engagement-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 mohitagw15856/pm-claude-skills --skill engagement-retro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engagement-retro --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/engagement-retro .gemini/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .gemini/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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 mohitagw15856/pm-claude-skills engagement-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 mohitagw15856/pm-claude-skills --skill engagement-retro -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/engagement-retro .github/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .github/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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 mohitagw15856/pm-claude-skills --skill engagement-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 mohitagw15856/pm-claude-skills engagement-retro --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/engagement-retro .opencode/skills/engagement-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 "engagement-retro" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engagement-retro into .opencode/skills/engagement-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engagement-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
engagement-retro- GitHub stars
- 1.4k
- Token cost
- ~935 tokens
- SKILL.md length
- 461 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path.
- Asked to wrap up a client project
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Run an engagement retro
What it does
Engagement Retro is an agent skill from mohitagw15856/pm-claude-skills. Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Use when asked to wrap up a client project, run an engagement retro, write a project close-out, or plan the follow-on. Produces a close-out — outcomes vs. goals, what worked / what didn't, profitability/scope reality, a reusable lessons log, and the next-engagement or referral ask.
Its SKILL.md is about 940 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 wrap up a client project
- Run an engagement retro
- Write a project close-out
- Plan the follow-on
Example prompts
- “/engagement-retro”
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
Engagement Retro loads about 935 tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 461 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). 461 words, ~935 tokens.
Download SKILL.mdSave it as
.claude/skills/engagement-retro/SKILL.md (or your agent's skills folder).- name
- engagement-retro
- description
- Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Use when asked to wrap up a client project, run an engagement retro, write a project close-out, or plan the follow-on. Produces a close-out — outcomes vs. goals, what worked / what didn't, profitability/scope reality, a reusable lessons log, and the next-engagement or referral ask.
Engagement Retro Skill
The end of an engagement is the highest-leverage, most-wasted moment in consulting: the client is happy (hopefully), you've learned things, and the next sale is easiest now. This skill runs the close-out — honest results vs. goals, what to repeat/fix, whether it actually made money, and the explicit renewal/ referral ask — so each engagement compounds into the next instead of just ending.
Required Inputs
Ask for these only if they aren't already provided:
- The engagement — what it was, the original goals/SOW, and what was delivered.
- The outcome — results vs. goals, and the client's apparent satisfaction.
- The reality — scope changes, time vs. estimate, profitability (did the pricing hold?).
- The relationship — is there follow-on work, a testimonial, or referral potential?
Output Format
Engagement Close-out: [client / project]
1. Outcomes vs. goals — what you set out to do vs. what was delivered and achieved. Honest, with the client's view.
2. What worked — the approaches, decisions, and moments to repeat next time (your reusable playbook grows here).
3. What didn't — scope creep, mis-estimates, friction, anything that hurt margin or the relationship — and the specific change for next time (process, SOW clause, pricing).
4. Commercial reality — did the engagement make money? Actual time vs. priced, scope changes captured (or eaten), effective rate achieved. The number that tells you whether to do this kind of work again, and at what price.
5. Lessons log — 2–4 transferable lessons to carry into your standard process / proposal / SOW (e.g. "add an acceptance window clause," "price discovery separately").
6. Grow the relationship — the explicit next step: the follow-on/renewal to propose, the testimonial to request (while they're happy — pair with case-study-writeup), and the referral ask ("who else do you know wrestling with this?"). Don't let a good engagement just end.
Show full SKILL.md (171 more words)Show less
Quality Checks
- Outcomes are assessed honestly against the original goals (not just "went well")
- What-worked and what-didn't each yield a specific repeat/change action
- Commercial reality is faced — actual vs. priced time, effective rate, scope eaten
- Lessons are written to feed back into the process/proposal/SOW
- Ends with concrete renewal, testimonial, and referral asks
Anti-Patterns
- Do not skip the money question — "the client was happy" but you lost margin means change the pricing, not repeat it
- Do not write vague lessons — "communicate better" isn't actionable; "add a weekly written status" is
- Do not let the engagement end without asking for the testimonial/referral — now is the easiest it'll ever be
- Do not bury scope creep — name what you ate so the next SOW prevents it
- Do not treat the retro as internal-only — the client-facing close-out also sets up the renewal
Based On
Consulting close-out / retrospective practice — outcome review, profitability reality, lessons-to-process, and the renewal/referral motion.
Example Trigger Phrases
- "Wrap up a client project."
- "Run an engagement retro."
- "Write a project close-out."
- "Plan the follow-on."
© 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/engagement-retro of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Engagement 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 |
|---|---|---|---|---|---|---|
| Engagement Retro this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~935 | 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 Engagement Retro
What does Engagement Retro do?
Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Engagement Retro is an agent skill from mohitagw15856/pm-claude-skills. Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path.
When should I use Engagement Retro?
Engagement Retro fits situations like: asked to wrap up a client project; run an engagement retro; write a project close-out; plan the follow-on.
How do I install Engagement Retro in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill engagement-retro -a claude-code`. Or copy the skill folder (skills/engagement-retro in mohitagw15856/pm-claude-skills) into .claude/skills/engagement-retro in your project. Claude Code loads it when a task matches its description.
How do I install Engagement Retro in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill engagement-retro -a codex`. Or copy the skill folder (skills/engagement-retro in mohitagw15856/pm-claude-skills) into .agents/skills/engagement-retro in your project. Codex loads it when a task matches its description.
Can I use Engagement 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 mohitagw15856/pm-claude-skills --skill engagement-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/engagement-retro, .gemini/skills/engagement-retro, .github/skills/engagement-retro and .opencode/skills/engagement-retro in your project.
What does Engagement Retro need to run?
SKILL.md names no scripts, command-line tools or credentials: Engagement Retro is instructions for the agent only.
Does Engagement 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 Engagement 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 Engagement Retro use?
Engagement 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 Engagement Retro use?
About 935 tokens (SKILL.md is roughly 3.7k 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 Engagement Retro?
Skills that share tags, products or a category with Engagement Retro: 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 Engagement Retro?
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.