How do I install the Retro skill?

Run npx skillmds@latest add huytieu/retro in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Retro safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Retro?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Retro free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

huytieu (@huytieu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Retro by huytieu — Agent Skill

Name: Retro
Rating: 4.5 (4 reviews)
Author: huytieu

File contents

/retro — CP-7 close the V

Every non-tiny shipped or escalated run gets a retro. Retro is advisory but strongly expected: it is how the harness improves.

When to run

After CP-6 ship (approved publish, merged PR, vault deliverable done)
After escalate (capture why verifier failed)
End of an /ultragoal phase (one retro per phase)
Manual: /retro <run-dir or spec path>

Phase 1 — Gather evidence bundle

Read:

Spec or card description + acceptance criteria
04-projects/harness/runs/<id>/evidence/ (ledger, checkpoints.tsv, CP-* files)
.claude/logs/loop-ledger.tsv (last rows for this run)
04-projects/<goal>/STATUS.md if an ultragoal phase

Phase 2 — Checkpoint audit

For each CP the lane required, mark Expected vs Actual vs Gap:

CP	`tiny`	`normal`	`full`
CP-1 spec	skip	required	required
CP-3v component	skip	required	required
CP-4 integration	skip	skip	required if multi-task
CP-5 acceptance	if mutate	required	required
CP-6 ship	if external	if external	required

Phase 3 — Evidence quality pass

Ask:

Any AC-n shipped without a PASS evidence row? (traceability violation)
Any PASS row where observation is tool-return not artifact? (confident-but-unchecked)
Any criterion that wasn't falsifiable? (fix in next spec)

Phase 4 — Write retro

Copy references/retro-template.md to:

04-projects/harness/retro/YYYY-MM-DD-<slug>.md

Fill all sections. Action items get IDs (AI-01…).

Phase 5 — Feed forward

Harvest: append action items + lessons to today's harvest staging
Backlog: add AI-n rows to 04-projects/harness/BACKLOG.md if harness work
STATUS.md: if an ultragoal phase, advance the phase state + log open AC-n
Spec checkpoint log: update spec ## Checkpoint log CP-7 row
Record: bash .claude/lib/checkpoint.sh record <run-dir> CP-7 PASS "retro: <path>"

Output to the user

TL;DR: outcome, top lesson, top action item, retro path.

---name: retrodescription: CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.---# /retro — CP-7 close the VEvery non-`tiny` shipped or escalated run gets a retro. Retro is **advisory** but strongly expected: it is how the harness improves.## When to run- After CP-6 ship (approved publish, merged PR, vault deliverable done)- After escalate (capture why verifier failed)- End of an `/ultragoal` phase (one retro per phase)- Manual: `/retro <run-dir or spec path>`## Phase 1 — Gather evidence bundleRead:1. Spec or card description + acceptance criteria2. `04-projects/harness/runs/<id>/evidence/` (ledger, checkpoints.tsv, CP-* files)3. `.claude/logs/loop-ledger.tsv` (last rows for this run)4. `04-projects/<goal>/STATUS.md` if an ultragoal phase## Phase 2 — Checkpoint auditFor each CP the lane required, mark Expected vs Actual vs Gap:| CP | `tiny` | `normal` | `full` ||---|---|---|---|| CP-1 spec | skip | required | required || CP-3v component | skip | required | required || CP-4 integration | skip | skip | required if multi-task || CP-5 acceptance | if mutate | required | required || CP-6 ship | if external | if external | required |## Phase 3 — Evidence quality passAsk:- Any AC-n shipped without a PASS evidence row? (traceability violation)- Any PASS row where observation is tool-return not artifact? (confident-but-unchecked)- Any criterion that wasn't falsifiable? (fix in next spec)## Phase 4 — Write retroCopy `references/retro-template.md` to:`04-projects/harness/retro/YYYY-MM-DD-<slug>.md`Fill all sections. Action items get IDs (`AI-01`…).## Phase 5 — Feed forward1. **Harvest**: append action items + lessons to today's harvest staging2. **Backlog**: add `AI-n` rows to `04-projects/harness/BACKLOG.md` if harness work3. **STATUS.md**: if an ultragoal phase, advance the phase state + log open `AC-n`4. **Spec checkpoint log**: update spec `## Checkpoint log` CP-7 row5. Record: `bash .claude/lib/checkpoint.sh record <run-dir> CP-7 PASS "retro: <path>"`## Output to the userTL;DR: outcome, top lesson, top action item, retro path.

Frequently asked questions

Retro