
Retro
Capture one small lesson from an agent session into .agents/learnings/ without running a full post-mortem or council-style review.
Overview
retro is a journey-wide agent skill that quick-captures a single useful observation into .agents/learnings/—usable whenever a solo builder needs to preserve a small lesson before the handoff without a full post-mortem.
Install
npx skills add https://github.com/boshu2/agentops --skill retroWhat is this skill?
- Writes a single observation to .agents/learnings/ with minimal ceremony (lighter than /post-mortem)
- Treats each capture as a candidate learning—promotion to pattern or rule happens later via the ratchet
- No council or transcript mining—direct one-insight capture into result.json semantics
- Executable spec positions retro as the lightest move-7 surface in the AgentOps hexagon
- Move 7 quick-capture surface in the AgentOps loop (lighter than full /post-mortem)
Adoption & trust: 842 installs on skills.sh; 384 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You noticed something that would help the next agent run but it is too minor for a formal post-mortem and easy to lose in chat.
Who is it for?
Agent-heavy solo workflows using AgentOps-style .agents directories who want frictionless learning capture after routine tasks.
Skip if: Major incidents, multi-root-cause reviews, or teams that need council-mediated transcript mining instead of one-line captures.
When should I use this skill?
You have one insight too small for /post-mortem but too useful to leave only in the session handoff.
What do I get? / Deliverables
A single learning entry lands in .agents/learnings/ as a ratchet candidate while promotion to patterns or rules stays a separate step.
- New or updated entry under .agents/learnings/
- Capture metadata consistent with result.json recording
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Log a prompt pattern that reduced hallucinated file paths after a refactor.
Note a checklist step you skipped so the next release review catches it.
Record a log query that surfaced the real error faster than the default dashboard.
Capture a scope trap you hit so the next idea pass avoids the same MVP creep.
How it compares
The lightest move-7 capture in AgentOps—use instead of /post-mortem when the insight is one observation, not an incident review.
Common Questions / FAQ
Who is retro for?
Solo and indie builders running AgentOps-style agent loops who want durable learnings on disk without spinning up a full retrospective workflow.
When should I use retro?
Use it after any phase when a single insight appears—Build debugging tricks, Ship launch gotchas, Operate monitoring notes, or Validate scope lessons—when a full post-mortem would be overkill.
Is retro safe to install?
It writes under .agents/learnings/ in your repo; review what you capture for secrets and check the Security Audits panel on this page before automating in shared repositories.
SKILL.md
READMESKILL.md - Retro
# Executable spec for the /retro skill — lightest learning capture (BC1 Corpus, loop Move 7). # /retro quick-captures a SINGLE observation into .agents/learnings/ — for an insight too small # to warrant a full /post-mortem but too useful to leave in the handoff. The captured entry is a # candidate; the promotion ratchet still decides whether it becomes a pattern/rule. Hexagon: # domain; consumes: standards; produces: result.json. (soc-qk4b) Feature: Retro is the lightest single-observation learning capture As the move-7 quick-capture surface I want a single insight written to the learnings store with minimal ceremony So that small-but-useful observations are not lost in the handoff Scenario: a single observation is captured to the learnings store Given an insight too small for a full /post-mortem but worth keeping When /retro runs Then the observation is written to .agents/learnings/ (result.json records the capture) Scenario: a captured entry is a candidate, not yet promoted When a retro entry is captured Then the promotion ratchet still applies — it is a candidate learning, not yet a pattern or rule And promotion to a pattern/rule happens later under the ratchet, not at capture time Scenario: retro is lighter than post-mortem and forge Then /retro captures one observation directly (no council, no transcript mining) And it is the lightest of the move-7 capture surfaces #!/usr/bin/env bash set -euo pipefail SKILL_DIR="$(cd "$(dirname "$0")/.." && pwd)" PASS=0; FAIL=0 check() { if bash -c "$2"; then echo "PASS: $1"; PASS=$((PASS + 1)); else echo "FAIL: $1"; FAIL=$((FAIL + 1)); fi; } check "SKILL.md exists" "[ -f '$SKILL_DIR/SKILL.md' ]" check "SKILL.md has YAML frontmatter" "head -1 '$SKILL_DIR/SKILL.md' | grep -q '^---$'" check "SKILL.md has name: retro" "grep -q '^name: retro' '$SKILL_DIR/SKILL.md'" check "SKILL.md mentions .agents/learnings/ output" "grep -q '\.agents/learnings/' '$SKILL_DIR/SKILL.md'" check "SKILL.md mentions learning categories" "grep -qi 'category\|debugging\|architecture\|process' '$SKILL_DIR/SKILL.md'" check "SKILL.md mentions post-mortem delegation" "grep -qi 'post-mortem' '$SKILL_DIR/SKILL.md'" echo ""; echo "Results: $PASS passed, $FAIL failed" [ $FAIL -eq 0 ] && exit 0 || exit 1 --- name: retro description: Capture a session learning. practices: - sre - lean-startup - dora-metrics hexagonal_role: domain consumes: - standards produces: - result.json context_rel: - kind: shared-kernel with: standards skill_api_version: 1 metadata: tier: knowledge dependencies: [] context: window: fork output_contract: .agents/learnings/YYYY-MM-DD-*.md --- # Retro Skill **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** Quick-capture a learning to the knowledge flywheel. For comprehensive retrospectives with backlog processing, activation, and retirement, use `/post-mortem`. ## Loop position Lightest capture surface for move **7** of the [operating loop](../../docs/architecture/operating-loop.md). Single-observation quick-capture into `.agents/learnings/`. Use when an insight is too small to warrant a full `/post-mortem` and too potentially-useful to leave in the handoff. The [promotion ratchet](../../docs/architecture/operating-loop.md#the-promotion-ratchet) still applies after capture — a retro entry is a candidate learning, not yet a pattern or rule. ## Quick Mode Given `/retro --quick "insight text"` or `/retro "insight text"`: 1. Generate a slug from the content: first meaningful words, lowercase, hyphens, max 50 chars. 2. Resolve the active bead with `timeout_run 1 bd current 2>/dev/null || echo ""`. 3. Write directly to `.agents/learnings/YYYY-MM-DD-quick-<slug>.md`: ```markdown --- type: learning source: retro-quick source_bead: <active bead id when available> source_phase: validate date: YYYY-MM-DD maturity: provisional utility: 0.5 --- # Learning: <Short Title> **Category**: <auto-classify: debugging|architecture|process|testi