retro

Collect project data and generate structured retro reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill retro-indigoai-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/retro
Command: npx skills add https://github.com/indigoai-us/hq --skill retro-indigoai-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to review past work to surface recurring patterns, capture actionable learnings, and feed improvements back into future projects or sessions.

Core Features & Use Cases

  • Supports PROJECT mode (completed projects) and SESSION mode (recent work sessions) for flexible retros.
  • Automates data collection from project docs, commit history, and collaboration threads to surface actionable patterns and learnings.
  • Generates a structured retro report (outputting to workspace/reports/{slug}-retro.md) that guides future work and learning capture.

Quick Start

Provide the project or session context and ask HQ to run a retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a retrospective to extract actionable learnings from a completed project?

To run a retrospective, provide the project context to trigger PROJECT mode, which collects data from project documentation, commit history, and collaboration threads to detect patterns and output a structured retro report.

What is the difference between project retros and recent work session analysis?

Project retrospectives analyze completed projects using PROJECT mode, while recent work session analysis uses SESSION mode to surface actionable learnings and recurring patterns from shorter collaboration threads and version history.

Can I automate data collection for team retrospectives from existing documentation?

Yes, retrospective automation collects data automatically from project docs, version history, and collaboration threads to surface actionable patterns and learnings, outputting a markdown retro report to guide future work.

What's the best way to detect recurring patterns across multiple team projects?

The best way to detect recurring patterns is running a retrospective in PROJECT mode, which aggregates documentation, version history, and collaboration threads to extract learnings and generate a structured team analysis report.

Do I need to manually prepare project documentation before running a retrospective?

No manual preparation is needed; the retrospective process automatically guides data collection from existing project documentation, commit history, and collaboration threads to detect patterns and extract learnings.

Where does the generated retrospective report get saved?

The retrospective report is generated as a structured markdown file and saved directly to the workspace reports directory at reports/{slug}-retro.md to guide future work and learning capture.