A retrospective report for a completed batch or milestone, where a milestone is a larger piece of planned work. It checks goals and contracts, compares planned tasks with delivered work, and suggests rule updates.

Use it after a batch or milestone to review reports, task lists, goals, contracts, and relevant Git history.

It turns completed work into a record of what was covered, skipped, or changed, making gaps and process improvements easier to see.

chief-retro — Skill for Claude Code by thaitype/chief

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add thaitype/chief --skill chief-retro

Clone the repo

git clone --depth 1 https://github.com/thaitype/chief

Made for: Claude Code.

Or install chief-skills, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thaitype/chief/chief-retro/github.svg)](https://agentmods.dev/skills/thaitype/chief/chief-retro)

Your own site

<a href="https://agentmods.dev/skills/thaitype/chief/chief-retro"><img src="https://agentmods.dev/badge/skills/thaitype/chief/chief-retro/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thaitype/chief/chief-retro"><img src="https://agentmods.dev/badge/skills/thaitype/chief/chief-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 741 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Memory Poisoning · line 76
Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.

Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.00741
Opus 5.5	$0.00018	$0.00296
Sonnet 5.5	$0.00009	$0.00148
Haiku 4.5	$0.00004	$0.00074

Measured 2mo ago against content hash 1d1ce2edc31f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chief-retro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/chief/chief-retro/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run a retrospective on the current milestone.

Scope Detection

Auto-detect the scope:

Read _plan/_todo.md in the active milestone.
If ALL tasks are marked [x] → milestone retro.
If some tasks remain → batch retro (covers only the latest completed batch).

Input Sources

Batch retro

Latest _report/autopilot-run-batch-<N>.md
_plan/_todo.md (completed vs remaining)
_goal/ and _contract/ files
git log for commits since the previous batch report (or milestone start)

Milestone retro

ALL _report/ files (batch reports, task outputs, etc.)
_plan/_todo.md (full history)
_goal/ and _contract/ files
git log for the entire milestone

Report Sections

Write the report with these sections:

# Retro: <milestone> — <batch N | milestone>

## Coverage Check

For each goal and contract file, check whether the work done satisfies it:

| File | Status | Notes |
|------|--------|-------|
| _goal/xxx.md | ✅ Satisfied / ⚠️ Partial / ❌ Missing | what's done or missing |
| _contract/xxx.md | ✅ / ⚠️ / ❌ | ... |

## Planned vs Delivered

- What was in the TODO
- What was actually completed
- What was skipped or changed mid-execution

## Blockers Hit

- Issues encountered during execution
- How they were resolved (or not)

## Lessons Learned

- Patterns observed (good and bad)
- Recurring problems
- Surprises or unexpected outcomes
- What worked well and should be repeated

## Proposed Rule Updates

For each proposal:
- **What:** the rule to add or change
- **Where:** which file in `.chief/_rules/` (e.g. `_standard/auth.md`, `_verification/tests.md`)
- **Why:** what happened that motivates this rule
- **Suggestion:** recommended for the user

## User Action Needed

Items requiring human decision:
- Uncovered goals or contracts that need another batch
- Decisions to promote to permanent rules
- Manual steps that automation couldn't handle

Output File

Batch retro → .chief/<milestone>/_report/retro-batch-<N>.md
Milestone retro → .chief/<milestone>/_report/retro-milestone.md

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 103 lines · 44 tokens per session scan A 1d1ce2edc31f

Subscribe to this mod's changes

chief-retro is a skill published in the GitHub repository thaitype/chief (68 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 741 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

chief-retro next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
chief-retrothaitype/chief	Skill	68	1mo ago	MIT	A	44	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code