retrolisted

The user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs. ## Steps 1. Call the Skill tool with "writing-for-agents" for the writing style guide. 2. Read the primary sources for the session the user specifies, defaulting to the current one. Your context holds at most the current session's main thread since its last compaction; everything else is on disk. Claude Code keeps sessions under `~/.claude/projects/` (or `$CLAUDE_CONFIG_DIR/projects/`), with sub-agent transcripts in `<stem>/subagents/` beside the session file, where `<stem>` is that `.jsonl` file's name. The current session is the newest `.jsonl` in the project's directory (`ls -t`): after a resume its name differs from the session ID your environment reports, so take `<stem>` from the file, never from that ID. Codex keeps them under `~/.codex/sessions/` (or `$CODEX_HOME/sessions/`). Dispatch one sub-agent to search what your context lacks (the part before any compaction, and every sub-agent transcript) and return only the friction excerpts: errors, denials, retries, corrections, each with its file and line. Count a repeated mistake across all of them before step 4 judges whether it recurs. Done when every source outside your context has been searched, or the session has no compaction and no sub-agents. 3. Look for candidates for improvement in these categories. - **Navigation**: how easy was it for the agent to find the right files? A