retro

A retrospective improves the agent's environment — the files, checks and tools the next session starts from — using one session as evidence. The code the session produced is evidence, not the subject: the friction it hit and the overbuild it shipped are.

A retro returns at most three fixes, often fewer. Every proposed rule is one more line every later agent reads, so a retro that proposes a fix for every friction point adds sediment instead of removing waste. The human should be able to approve the whole list without weighing each item.

Invocation: retro (the current session) · retro <slug> (a .workflow/<slug>/ run) · retro <session id>.

Steps

1. Load the writing guides. Invoke the agent-docs skill: its vocabulary (context pointer, no-op, sprawl, cache, single source of truth) is how candidates are judged and worded. Invoke the plain skill too: the report to the human follows its Rules.