analyze-session

# 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, and the `commit` skill owns whatever lands as a change. ## Which session `$ARGUMENTS` holds the absolute path to the transcript. A bare session ID also works, provided it names 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: open the task list Create these tasks with `TaskCreate`, then move each to `in_progress` and `completed` as you go. They're the checklist the rest of this document expands. 1. Read what the line numbers identify 2. Test the session's own conclusions 3. Verify every figure with three agents 4. Recommend fixes across the five areas 5. Write the retrospective Stop before any of it where preflight couldn't resolve the transcript, or reports a missing precondition. Say what's wrong and hand back. The preflight already resolved the transcript and summarized the session. It created the retro directory at `<main worktree>/.claude/retros/YYYYMMDD_<session ID>/` and copied the evidence into it. Read that report befor...