Verified:GitHub

dharma-retro

Generates structured retrospectives with wins, misses, root causes, and next actions from completed work.

1|3|Updated Mar 9, 2026

Search Tags:#root cause analysis #retrospective #post-mortem #continuous improvement #team learning #incident review

One-click install

npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-retro-aikagrya

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: dharma-retro
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/retro
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-retro-aikagrya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a project, release, or incident, teams often skip reflection or run unfocused retros that produce blame and vague takeaways. This Skill enforces a disciplined retrospective format that converts completed work into concrete system improvements. ## Core Features & Use Cases - Structured Retrospective Output: Produces four mandatory sections: wins, misses, root causes, and next actions. - Blame-Free Analysis Rules: Enforces no blame theater, no empty praise, and a preference for system learning over personal narratives. - Downstream Handoff: Feeds findings into review and incident workflows such as engineering review, executive review, or incident command processes. - Use Case: After shipping a release that included a production outage, run this mode to document what worked, what failed, why it failed, and which concrete actions should improve the next cycle. ## Quick Start Run a retrospective on the release we just finished and produce wins, misses, root causes, and next actions.

Frequently Asked Questions about dharma-retro

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

FAQPage Schema

How do I run a retrospective after a project or release?▼

Invoke this mode after completing a meaningful piece of work, release, or incident. It guides the analysis and produces four required sections: wins, misses, root causes, and next actions that improve the system.

What should a good retrospective output include?▼

A good retrospective includes what worked, what failed, the root causes behind failures, and concrete next actions. This Skill mandates exactly those four sections and prohibits blame framing and empty praise.

Can this be used for post-incident reviews?▼

Yes, the mode explicitly covers incidents alongside releases and general work. Its output is designed to hand off to incident commander and review workflows for follow-up action.

When should I not use a structured retrospective?▼

Skip it for trivial tasks with no meaningful learning potential, since the mode is intended for significant work, releases, or incidents. It also does not replace real-time incident response, only post-hoc analysis.