Claude Cursor 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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download huytieu-cog-second-brain-.claude_skills_retro-4cdb601.zip · 1 KB

huytieu/cog-second-brain 1236 147 forks MIT Updated 12h ago

Part of huytieu/cog-second-brain — 108 skills

Install

skills CLI npx skills add https://github.com/huytieu/COG-second-brain/tree/main/.claude/skills/retro

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install huytieu-cog-second-brain@llmmart

Git git clone https://github.com/huytieu/COG-second-brain.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole huytieu/cog-second-brain collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/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.

Files (cog-second-brain)

references

retro-template.md 867 B

# Retro: <run or spec>

> Date: YYYY-MM-DD · Run: `04-projects/harness/runs/<id>` · Lane: `<lane>` · Outcome: shipped | escalated | abandoned

## What happened

Two or three sentences. The sequence, not the narrative.

## Evidence quality

| AC | Had a PASS row | Observed the artifact | Notes |
|---|---|---|---|
| AC-01 | yes/no | yes/no: what was observed | |

Any `PASS` that rested on a worker's summary instead of the artifact is a finding, not a pass.

## What the gates caught

| CP | Verdict | What it caught, or why it was silent |
|---|---|---|

## Friction

Where the run lost time or nearly went wrong. One line each, concrete.

## Actions

`AI-n` rows go to `04-projects/harness/BACKLOG.md`. Skill or `CLAUDE.md` patches are proposed here, applied only with approval.

| ID | Action | Target file | Status |
|---|---|---|---|
| AI-1 | | | proposed |

SKILL.md 2.2 KB

---
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.