running-retros
Running retros
A long session teaches things that die with it: missing guidance, a command that cost four retries, work no skill describes. This skill proposes each durable learning as a change the user can accept or reject.
Bare /running-retros mines this session. A prompt points it elsewhere:
/running-retros read my last 10 sessions and find where agents took too long to find things,
or
/running-retros read my team's PR review comments and suggest CODING_STANDARDS.md updates.
The prompt picks the question, the sources, and the targets.
Reading an OpenCode store needs a Node.js that loads node:sqlite without a
flag (22.13 or later); otherwise the run stops with sqlite-unavailable.
Tracker sources and issue filing need an authenticated gh; without it, those
sources are reported unread and backlog items print unfiled.