retro

Analyze AI session dialogue to identify blockers and generate a Markdown retrospective report.

10|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill retro-warlikelaux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/WarLikeLaux/yii2-book-catalog/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill retro-warlikelaux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and resolve bottlenecks, context losses, and inefficiencies in AI-assisted work sessions, leading to a smoother and more productive workflow.

Core Features & Use Cases

  • Session Analysis: Reviews dialogue history to pinpoint blockers, time losses, and successful patterns.
  • Report Generation: Creates a structured Markdown report detailing session findings and actionable suggestions.
  • Contract & Skill Updates: Facilitates direct updates to AI contract and skill definitions based on retrospective insights.
  • Use Case: After a complex coding session, use this Skill to analyze what went wrong, document recurring issues like "misunderstanding requirements," and propose specific changes to the AI's contract.md to prevent future errors.

Quick Start

Run the retro skill to analyze the current session and generate a retrospective report.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I analyze an AI session to identify context loss and workflow blockers?

Session analysis reviews dialogue history to pinpoint blockers, context losses, and time inefficiencies. It evaluates your AI interactions to find successful patterns and generate actionable suggestions for improving your overall workflow.

Can I generate a retrospective report to document recurring AI coding issues?

You can generate a retrospective report to document recurring issues like misunderstood requirements. The Skill creates a structured Markdown report in the docs/retro/ directory detailing session findings and proposing specific workflow improvements.

How do I update an AI contract based on session retrospective insights?

Updating an AI contract based on retrospective insights involves reading docs/ai/contract.md and applying generated suggestions. The Skill facilitates direct updates to contract definitions to prevent future errors and resolve identified bottlenecks.

What's the best way to prevent context loss during complex AI-assisted work sessions?

Preventing context loss during complex sessions requires conducting a retrospective analysis after work concludes. This identifies specific dialogue bottlenecks and produces actionable suggestions to refine AI skills and prevent recurring inefficiencies.

Do I need a specific AI contract file to run a session retrospective?

Yes, you need an existing AI contract file to run a session retrospective. The Skill requires reading docs/ai/contract.md to analyze current definitions and propose targeted updates based on the session's dialogue history.

Why does my AI workflow keep hitting the same blockers during extended coding sessions?

Recurring blockers happen when context losses and inefficiencies go unanalyzed. Conducting a retrospective analysis evaluates your dialogue history to identify these specific patterns and generates suggestions to update the AI contract for future prevention.