Weekly Engineering Retro skill for Claude and Codex

Weekly Engineering Retro as an AI skill. It asks for Week covered, Commit log or merged PRs, Incidents and alerts and 3 more, then does the rest. Free to…

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

Use when an engineering lead needs a short weekly retrospective built from commit history and incident records instead of from memory. Do not use for post-incident reviews for a single outage or annual performance reviews. Related topics: productivity, coding.

What it will ask you for

• Week covered (free text, e.g. "Date range")
• Commit log or merged PRs (longer free text)
• Incidents and alerts (longer free text)
• Goals set last week (longer free text)
• Team mood or blockers (longer free text)
• Audience (choose one: Team only, Team and manager, Wider company)

How it works

1. Group the week's commits into themes and write what shipped in plain language.
2. Compare the results with last week's goals and mark each as met, partly met, or missed.
3. List what hurt, with numbers for incidents, review waits, and rework, and name the likely root cause of the biggest pain.
4. Choose exactly one change for next week with an owner and a success signal.
5. Keep the retro under 400 words and finish with next week's proposed goals.

What you get

A retro under 400 words with sections for shipped work, goals status, what hurt, one change with owner and signal, and next week's goals.

What it watches out for

• Proposing five improvements, so none of them happens.
• Naming individuals in the 'what hurt' section, which turns a retro into blame.
• Listing commits one by one instead of summarising by theme.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.