retro

Generate retro reports from Pi session logs and orchestration artifacts.

6|Updated Feb 25, 2026

Search Tags:#automation #documentation #agent logs #postmortem #workflow improvement #retro

Ready to run

npx skills add https://github.com/l3wi/agents-workflow --skill retro-l3wi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/l3wi/agents-workflow/tree/main/.pi/skills/retro
Command: npx skills add https://github.com/l3wi/agents-workflow --skill retro-l3wi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and learn from past workflow executions, turning agent mistakes and failures into actionable improvements for documentation and automation.

Core Features & Use Cases

Failure Analysis: Pinpoints tool failures, merge issues, and validation errors from session logs.
Artifact Correlation: Links session logs with orchestration artifacts for a comprehensive review.
Improvement Proposals: Generates concrete suggestions for documentation, template updates, and automation gaps.
Use Case: After a complex multi-agent feature development cycle, use this Skill to analyze why certain tasks failed and generate a report detailing how to update the task templates to prevent similar issues in the future.

Quick Start

Generate a retro report for the 'user-authentication' feature using the latest session logs.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate retrospectives from agent session logs?▼

To generate retrospectives from agent session logs, you analyze Pi session logs and orchestration artifacts. This process identifies tool failures, merge issues, and validation errors, correlating them with orchestration data to output detailed retro reports and action items for workflow enhancement.

What is the best way to analyze tool failures and validation errors from past workflow executions?▼

The best way to analyze tool failures and validation errors is by correlating session logs with orchestration artifacts within a specified timeframe. This approach pinpoints specific workflow failures and generates concrete suggestions for template updates and automation gaps.

Can I use session logs to propose concrete documentation improvements for multi-agent feature development?▼

Yes, you can use session logs to propose concrete documentation improvements. By analyzing agent mistakes and orchestration data from complex multi-agent feature development cycles, the system generates detailed reports on how to update task templates to prevent similar issues.

How do merge failures in orchestration artifacts get correlated during a retrospective analysis?▼

Merge failures in orchestration artifacts are correlated by analyzing session logs against the orchestration data within specified timeframes. This links the specific failure events with the broader workflow execution context to produce comprehensive retro reports.

Does this workflow improvement process work without additional dependencies?▼

Yes, the workflow improvement process works without additional dependencies. It operates independently using scripts and references to analyze session logs and orchestration artifacts, generating actionable retrospectives and improvement proposals without requiring external packages.