retrospective

Analyze post-failure events and generate durable process fixes.

6|1|Updated Apr 26, 2025
One-click install
npx skills add https://github.com/edobry/minsky --skill retrospective-edobry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/edobry/minsky --skill retrospective-edobry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and analyzes post-failure events to produce durable process fixes that prevent recurring issues.

Core Features & Use Cases

  • Structured, step-by-step retrospective workflow that guides incident identification, root-cause analysis, and durable artifact changes.
  • Auto-triggers on correction signals and repetitive feedback to surface systemic process weaknesses.
  • Clear guidance for memory persistence and CLAUDE.md alignment to enforce improvements.

Quick Start

Examine the latest failure and follow the six-step protocol to generate a durable fix.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I conduct a structured post-mortem after a process failure?

A structured post-mortem uses a six-step retrospective workflow to identify failures, perform root-cause analysis, and generate durable process fixes that prevent recurring issues.

When do I need root-cause analysis for missed post-merge issues?

Root-cause analysis is needed when post-merge audits reveal missed issues or when subagents produce incomplete work, triggering a retrospective to surface systemic process weaknesses.

How do I stop repeating feedback and recurring process failures?

To stop recurring failures, auto-trigger a retrospective on correction signals to analyze the events and enforce durable artifact changes aligned with your memory and CLAUDE.md.

Does process improvement integrate with memory and CLAUDE.md?

Yes, process improvement integrates directly with memory and CLAUDE.md alignment to persist durable fixes and enforce continuous quality assurance improvements across workflows.

What is the best way to ensure fixes from a retrospective are durable?

The best way to ensure durable fixes is following the structured six-step protocol, which guides incident identification through to durable artifact changes and memory integration.