retro

Analyze completed agent session transcripts to produce structured retro findings and improvement proposals.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill retro-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/retro
Command: npx skills add https://github.com/kanade0404/dotfiles --skill retro-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed agent sessions into structured retro analysis so you can understand why the harness behaved the way it did and what to improve next.

Core Features & Use Cases

  • Transcript Review: Analyzes a session transcript from a fresh subagent perspective to reduce self-bias.
  • Operational Diagnostics: Identifies tool usage patterns, permission denials, loop or stall behavior, skill misfires, token waste, and blocking waits.
  • Improvement Planning: Maps each finding to the right lever, such as hooks, allow/deny settings, skill edits, new skills, or rule and prompt tuning.
  • Use Case: After a PR is merged or a long session ends, use this Skill to produce prioritized recommendations for improving agent reliability and workflow quality.

Quick Start

Ask the retro skill to analyze the latest completed session transcript and return prioritized harness improvement proposals without making any edits.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I analyze agent session transcripts to find why the harness stalled or wasted tokens?

Session transcript analysis inspects completed agent runs to identify tool usage patterns, permission denials, and loop behavior. It maps each operational finding to specific harness improvement levers like hooks, allow/deny settings, or skill edits.

What is the best way to review a misfired skill after a long agent session ends?

Reviewing a misfired skill requires analyzing the session transcript from a fresh subagent perspective to reduce self-bias. This diagnostic approach identifies skill misfires, token waste, and blocking waits, then maps them to rule, prompt, or skill tuning recommendations.

Can I get structured improvement proposals for agent reliability without making code edits?

Yes, you can generate structured retro findings and harness improvement proposals without applying edits. The analysis reviews tool statistics, permission denials, and session behavior to return prioritized recommendations for workflow quality improvements.

How do I diagnose permission denials and blocking waits in completed agent sessions?

Diagnosing permission denials and blocking waits involves inspecting the completed session transcript and tool statistics. This operational diagnostic maps identified issues to the correct operational levers, such as allow/deny settings adjustments or new hook configurations.

When do I need to run a post-merge session review for agent workflow quality?

A post-merge session review is needed when a PR is merged or a long-running session ends, especially if a skill misfired or wasted tokens. It produces prioritized recommendations for improving agent reliability by mapping transcript findings to harness fixes.