retro
Deep blameless postmortem workflow—timeline, impact, root cause vs contributing factors, what went well/poorly, action items with owners, and follow-through. Use after incidents, outages, or near-misses to improve reliability culture.
Why use this skill?
Use the OpenClaw retro skill to facilitate blameless postmortems, perform deep-dive root cause analysis, and track actionable improvements for your engineering team.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/clawkk/retroWhat This Skill Does
The 'retro' skill provides a structured, blameless framework for conducting post-incident reviews. It guides the user through six systematic stages: defining scope and audience, documenting a precise UTC timeline, performing deep-dive root cause analysis (RCA), evaluating operational successes and failures, tracking concrete action items, and managing follow-up communication. By moving away from blame and focusing on systemic improvements, this skill helps teams build a resilient engineering culture that learns from outages, near-misses, and security incidents rather than simply patching symptoms.
Installation
To integrate this skill, run the following command in your terminal:
clawhub install openclaw/skills/skills/clawkk/retro
Use Cases
- Post-Incident Debriefs: Facilitate an objective discussion following a SEV-1 outage to ensure all stakeholders share the same factual understanding.
- Engineering Culture Building: Transition team retrospectives from finger-pointing exercises to collaborative problem-solving sessions.
- Compliance and Audit Readiness: Generate standardized, professional postmortem reports for stakeholders that detail root causes and verified remediation steps.
- Continuous Improvement: Track the efficacy of 'detect' vs. 'prevent' actions over time to identify chronic system weaknesses.
Example Prompts
- "Start a new retro for the API downtime incident from yesterday. Help me outline the timeline and identify the root cause using the five-whys method."
- "Review this draft postmortem for the database migration issue. Are the action items specific enough, and is the tone blameless?"
- "Summarize the action items from our last three incidents and create a report showing which ones are still pending their 30-day follow-up."
Tips & Limitations
- Psychological Safety: The success of this tool relies on leadership modeling vulnerability. If engineers fear reprisal, the data provided will be inaccurate.
- Match Depth to Severity: Do not over-engineer the process for minor, localized bugs; keep the rigor proportional to the impact.
- Security Coordination: Always verify with your Infosec or Legal teams before finalizing any externally-facing summary regarding security-sensitive incidents.
- Avoid Vague Tasks: An action item like 'Improve monitoring' is rejected by the system. Demand specific metrics, alerts, or thresholds instead.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-clawkk-retro": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Related Skills
data-move
Deep data migration workflow—scope, mapping, validation, batching and ordering, dual-write and cutover, rollback, and reconciliation. Use when moving tenants, bulk backfills, or changing stores without losing trust in data correctness.
data-model
Deep data modeling workflow—grain, facts and dimensions, keys, slowly changing dimensions, normalization trade-offs, and analytics query patterns. Use when designing warehouse/analytics models or reviewing star/snowflake schemas.
guard
Deep AI safety guardrails workflow—policy definition, input/output filtering, monitoring, escalation, and false-positive handling. Use when reducing harmful outputs, misuse, or policy violations in LLM products.
prompts
Deep prompt engineering workflow—task spec, constraints, examples, evaluation sets, iteration protocol, regression testing, and safety alignment. Use when improving LLM outputs, shipping prompt changes, or building reusable prompt templates.
cost-opt
Cloud cost review: rightsizing, reservations, waste. Use when reducing infra spend.