retro

Analyzes coding session logs to propose agent environment improvements.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill retro-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/retro
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill retro-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a coding session, it is hard to know why the agent struggled, made mistakes, or wasted tokens. This Skill conducts a structured retrospective on a session and turns observed friction into concrete improvements for the agent's environment, such as navigation pointers, automated checks, and coding standards. ## Core Features & Use Cases - Session Analysis: Reads primary sources like session logs to reconstruct what happened during a coding session, defaulting to the current session when none is specified. - Improvement Categories: Evaluates navigation, automated checks, coding standards, global AGENTS.md bloat, tool economy, no-op instructions, and information access, then ranks candidates by severity. - File Placement Guidance: Directs findings to the right destination, keeping CLAUDE.md/AGENTS.md minimal, routing rules to CODING_STANDARDS.md for the review agent, and using docs and skills for reference material. - Use Case: After a long session where the agent repeatedly failed to find a config file and made a lint-catchable error, run a retrospective to add a navigation pointer and a lint check so future sessions avoid both problems. ## Quick Start Ask the agent to run a retrospective on the last coding session and suggest improvements to the agent environment.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a retrospective on a coding agent session?▼

Invoke the retro skill and optionally specify which session to analyze. It reads the session logs, evaluates improvement categories like navigation and automated checks, and presents candidates ranked by severity.

What kinds of improvements does a coding session retrospective suggest?▼

It suggests navigation pointers, new automated checks like linting or tests, coding standards rules for the review agent, trimming of AGENTS.md, removal of no-op instructions, and better information access such as teed dev server logs.

Should coding standards go in AGENTS.md or a separate file?▼

Coding standards belong in CODING_STANDARDS.md, which is read during review, not implementation. AGENTS.md should stay minimal and contain mainly navigation pointers, since the implementation agent has the most context pressure.

What happens if I don't specify which session to analyze?▼

The skill defaults to the current session. It searches through session logs on the machine to find the primary sources for the session being reviewed.

When should I not use a session retrospective?▼

Skip it when the session had no friction, mistakes, or expensive tool calls worth analyzing. It is designed for improving the agent environment, not for reviewing code quality or product decisions.