retro
FeaturedBuild a session's learnings into the setup: its friction, what went wrong and why, then an improved instruction, route, hook or script, verified, or 'no setup change warranted'. Started by name only: /agent-harness:retro in Claude Code, $agent-harness:retro in Codex.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- phuryn
- Repository
- phuryn/product-engineering
- Created
- 2 weeks ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
retro
Review a finished coding session for what slowed the agent down or let a mistake through, and turn one lesson into a test, check or doc in the project so the next session does not repeat it. Use when the user asks for a retro or retrospective, a post-mortem of a session, or "what should we change so this doesn't happen again". To carry unfinished work into a new session, use `handoff`; to prove a fix before claiming it, use `regression-proof`.
retro
Look back over a Claude Code session and suggest changes to the working setup — checks, steering files, memory, skills, tooling — so the next session doesn't repeat its mistakes, worst first. Use for "retro", "retrospective", "what should we change after this session", or "why did that take so long". Args: optional session (default: the current one).
retro
Do a retrospective of a coding session and propose changes to the agent's environment: checks, navigation, steering files and tool cost. Use for /retro.