retro

Analyze completed epics to generate structured retrospectives with actionable recommendations.

2|3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/dot-do/dotdo --skill retro-dot-do
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/dot-do/dotdo/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/dot-do/dotdo --skill retro-dot-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze completed epics to generate structured retrospectives with actionable recommendations.

Core Features & Use Cases

  • Reads execution telemetry to compute efficiency scores and surface actionable improvements for agent prompts, debug knowledge, and workflow configuration.
  • Archives retrospectives for future reference and updates insights to guide subsequent epics.
  • Supports both single-epic analysis and multi-epic review via --recent invocations, with optional dry-run mode to preview changes.

Quick Start

Invoke /retro <epic-id> to run a retrospective and review recommended changes.

Frequently Asked Questions about retro

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

FAQPage Schema
Can I review multiple recent epics at once for workflow improvements?

Yes, you can review multiple recent epics by invoking the tool with the --recent flag. This analyzes recent epic histories to compute efficiency scores and generate actionable recommendations for agent prompts, debug knowledge, and workflow configuration across the batch.

Does the retrospective tool require user approval before applying workflow changes?

Yes, the retrospective tool requires explicit user approval before applying any workflow configuration changes. You can also use the optional dry-run mode to preview recommended changes to agent prompts and debug knowledge before committing them.

What happens to retrospective insights after an epic is analyzed?

After an epic is analyzed, retrospective insights are archived for future reference and centralized insights are updated to guide subsequent epics. This ensures workflow improvements and debug knowledge inform future development cycles.

Can I preview workflow configuration changes before applying them to an epic?

Yes, you can preview workflow configuration changes using the optional dry-run mode. This allows you to review recommended improvements to agent prompts and debug knowledge without committing any modifications to the epic.