← All skills · Automation · Retro Compiler

Retro Compiler — finished output
Runs inClaude Code Codex Cursor Muse Dot Grok Bot Cue OpenClaw Hermes
Needs:The retro notes: retro.txt (a Session line saying which sprint or period this retro covers, one Good line per thing that went well, one Problem line per thing that went wrong, one Action line per action item — text, then | Owner: <name> and | Due: <date> — and optional Note lines).

Similar Skills

View all skills →

What you get

  • A three-column retro document: Went well, Problems ranked by impact signals, and Action items
  • Every action with an owner and a due date — Unassigned and No due date shown, never hidden
  • Each problem with its signal count and the matched evidence words
  • Every gap, input error, and warning named in the report
  • A plain statement when the retro has problems but no actions — a complaint list, not a plan

Good fit

  • Closing a sprint, project, or period with a written retro that ends in owned work
  • Seeing which problem the team worded most strongly, before deciding what matters most
  • Carrying last retro's open problems into the next one instead of dropping them

Not for

  • Deciding what the worst problem is — the ranking counts signal words, not severity
  • Assigning work to people who did not agree to it — an action without an owner stays Unassigned
  • Running a retro with no notes — the report will list the gaps, not invent the retro

Sample output

An example of what this Skill produces. Sample content, shown for illustration.

Retrospective — sample

Good: 3 | Problems: 3 | Actions: 3 | Gaps: 0 | Errors: 0 | Warnings: 0

Ranked: 1. Deploy was blocked twice — the pipeline was down for two hours — 3 signals ('blocked', 'down', 'twice'); 2. Checkout failed for old accounts after the deploy — 1 signal ('failed'); 3. We waited a day for the API key — 1 signal ('waited').

Actions: Add a deploy smoke test — Mei, due 2026-11-20; Backfill old-account test data — Chen, due 2026-11-22; Put API keys in the shared vault — Lin, due 2026-11-18.

What this report is not: a retro is a record of what the team said, not a verdict — the ranking counts impact-signal words, not severity.

About this Skill

You say
Sprint 24 just ended — turn our retro notes into a document that ends in owned actions.

How to install

  1. Copy the install prompt into your agent: Read https://skillu.dev/install/agent.md, then install the Retro Compiler skill (retro-compiler).
  2. Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
  3. Call it with a slash command, e.g. /retro-compiler, and describe what you want in plain words.

FAQ

Does the top-ranked problem mean it is the worst problem?

No. It means that problem matched the most impact-signal words in the notes — it is the most worth discussing first, not necessarily the most severe. A quiet problem with no signal words can still be the one that matters. The ranking is a sorting aid, not a severity verdict.

What if an action has no owner?

It stays in the report as Unassigned, and the warnings name it. The report never assigns work to someone who did not agree to it — if an action has no owner, the retro has an open question, not a finished plan.

Get Premium access Browse more skills