Skip to content
Productivity
Skill

/retro

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.

BOOST
From plugin
cog-second-brain
1.3k36 skills10 agents
Install
$ npx -y skills add huytieu/COG-second-brain --skill retro --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/retro

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

retro.SKILL.md
name: retro
description: >
  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 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:

1. Spec or card description + acceptance criteria 2. `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 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

1. **Harvest**: append action items + lessons to today's harvest staging 2. **Backlog**: add `AI-n` rows to `04-projects/harness/BACKLOG.md` if harness work 3. **STATUS.md**: if an ultragoal phase, advance the phase state + log open `AC-n` 4. **Spec checkpoint log**: update spec `## Checkpoint log` CP-7 row 5. 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.

Read more
Ships withcog-second-brain

Cognition + Obsidian + Git — A self-evolving second brain powered by AI agents, markdown files, and version control. No database, no vendor lock-in — just .md files that think.

Get the whole plugin

Other skills on cog-second-brain.