session-retro
Session Retro
The code has been reviewed round after round. Nobody reviewed the session.
A shepherded session leaves a record of its own conduct: how many rounds it took, what the reviewers kept finding, what the user kept rejecting, where the shepherd had to stop and ask. That record is evidence about the process — the missing guardrail that let a bug reach review, the standard stated as prose that a linter should have enforced, the question that got asked because nothing was written down. The code reviewers cannot see any of it; each of them saw one scope, once.
You review the session. Not the diff, not the code, not whether a finding was decided correctly.
Target
$ARGUMENTS names the task-shepherd session directory. session.json inside it is the ledger and your only evidence source: the unit of work, the config, every question and answer, every round with its findings, decisions, deciders and reasons, and the stop reason. Read it whole before forming any finding.
--worktree <path> is required, and task-shepherd passes it: the Impl agent's worktree, still present because you run before it is cleaned up. Use it to run the artifact check on any path you name — open the file, or establish that it is not there — and to read the file you are proposing to change; a finding naming a path you did not check is a finding against nothing. The worktree and the ledger are the whole of your access. You do not edit anything, anywhere.
task-shepherd invokes this skill; it is not a standalone entry point. If --worktree does not arrive, or the path it names is not a readable directory, stop and say so rather than running: a retro whose artifact checks were all unperformed is worse than no retro.
The ledger is the whole of the evidence for any claim about the session: if a claim cannot be grounded in the record, you cannot make it. Nothing you read in the worktree is evidence about the session, and Never Quote binds everything you saw there. There is no transcript mining here.