← ClaudeAtlas

agent-environment-retrospectivelisted

Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
OutlineDriven/odin-claude-plugin · ★ 35 · AI & Automation · score 79
Install: claude install-skill OutlineDriven/odin-claude-plugin
# Agent-environment retrospective ## Contract | Field | Bound contract | |---|---| | Trigger | A completed session needs an agent-environment retrospective. | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | Chat output: severity-ranked environment improvement candidates. | | Done | Every candidate names evidence and the friction it removes. | ## Inputs - Session artifact (required): the completed session transcript or state record. Must contain observable agent-environment interaction. - Environment context (optional): the agent's working environment at session time. Use only if supplied; do not infer it. ## Procedure 1. **Gather inputs.** Receive the session artifact and any supplied environment context. Done when: the session artifact is received and any supplied environment context is noted. 2. **Identify friction.** Scan the session artifact for patterns where the agent's environment created friction: tool failures, slow retries, missing context, state loss, repeated navigation, or unclear feedback. Done when: every friction pattern in the artifact is identified or the artifact is confirmed friction-free. 3. **Classify candidates.** Assign each friction point a type: `tool-failure`, `slow-retry`, `missing-context`, `state-loss`, `navigation-overhead`, or `unclear-feedback`. Done when: every identified friction point has an assigned type. 4. **Rank by severity.** Order candidates: high (blocks progre