dev-retro

1# Retro
2 
3Turn what went wrong into fixes that stop it recurring. Not a status summary: use `session-compact` for handoff state.
4 
5## Rules
6 
7- When suggested by another skill, ask the user before running; skip silently if declined.
8- Every item needs evidence: a failed command, hook or test output, a user correction, a revert, or rework in the diff. No generic lessons.
9- Cap at the 3-5 highest-cost items. Note what worked in one line only if it should be kept on purpose.
10- Blameless: describe the gap in the system, not the person or agent.
11- Never copy secrets, credentials, or personal data from transcripts into fixes or memory.
12 
13## Fix Ladder
14 
15Pick the highest rung that works:
16 
171. Automate: test, lint rule, hook, CI check, build dependency.
182. Fix the tool: script, template, default config.
193. Instruct: skill, `AGENTS.md` / `CLAUDE.md`, docs.
204. Remember: `memory` entry, only for knowledge that cannot be enforced. Search first; update instead of duplicating.
215. Drop: one-off with no pattern.
22 
23## Workflow
24 
251. Scope the work: feature, branch, session, or incident, and its commit range.
262. Gather evidence: `git log` and diff for the range, failed or retried commands, hook/CI failures, `task` evidence, user corrections. Use the session transcript when available (`agent sessions`, `session-compact`); do not require it.
273. For each item, record: what happened, cost (time, rework, risk), root cause in one line, and the fix with its rung, exact file or command.
28…