Analyze a session

Work the steps in order. This skill ends once the retrospective exists on disk and the operator has its path. Acting on what it recommends is separate work. Use the commit skill for any change that comes out of it.

Which session

$ARGUMENTS holds the absolute path to the transcript. A bare session ID also works, provided it matches exactly one file under ~/.claude/projects/.

If you give neither, the preflight says so and prints how to find it. Send a Haiku subagent, then run the preflight again with the path it returns. Never search the projects directory yourself. Reading transcripts to find one costs more context than the entire analysis that follows it.

Preflight

!bash ${CLAUDE_SKILL_DIR}/scripts/preflight.sh ${ARGUMENTS}

Step 0: the checklist

Track these steps with the session's task-list tools where it has them. Newer harnesses leave those tools out by default, and a session without them works the list in order as written. They're the checklist the rest of this document expands.