skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
huytieu/cog-second-brain95 installs

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.

How do I install this agent skill?

npx skills add https://github.com/huytieu/cog-second-brain --skill retro
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill facilitates project retrospectives by auditing evidence and updating logs. It executes a local shell script and processes external project files, which introduces minor risks related to command execution and indirect data processing.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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

CPtinynormalfull
CP-1 specskiprequiredrequired
CP-3v componentskiprequiredrequired
CP-4 integrationskipskiprequired if multi-task
CP-5 acceptanceif mutaterequiredrequired
CP-6 shipif externalif externalrequired

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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/huytieu/cog-second-brain/retro">View retro on skillZs</a>