Results for “blameless”

Use when working with Blameless — blameless incident management, SLO tracking, retrospectives, and reliability insights. Covers incident lifecycle, blameless retrospective facilitation, follow-up tracking, reliability scorecards, and incident type categorization. Use when managing active incidents, conducting retrospectives, tracking SLO compliance, or analyzing reliability trends in Blameless.

The English summary is being prepared. Showing the original description.

Manage service incidents from initial assessment through recovery review. The skill organizes severity, impact, roles, status updates, and timelines, then drafts a blameless postmortem with root cause analysis and action items assigned to owners.

• Assess the severity and impact of a new incident
• Draft internal and customer status updates
• Record mitigation steps and an incident timeline

Manage service incidents from initial assessment through recovery review. The skill organizes severity, impact, roles, status updates, and timelines, then drafts a blameless postmortem with root cause analysis and action items assigned to owners.

• Assess the severity and impact of a new incident
• Draft internal and customer status updates
• Record mitigation steps and an incident timeline

Use this skill when an incident or a serious near miss is closed and the team must learn from it, or an auditor asks for lessons learned, and someone says "run the post-mortem", "post-incident review", "lessons learned", "retro on the outage", "blameless review", "root cause of the incident" or "what do we change after this breach". Builds the timeline from records before the meeting, runs a blameless discussion, finds the contributing factors, and turns them into a few owned, dated actions linked to updates of the risk register, controls, playbooks and supplier records, then writes the review and an action tracker.

The English summary is being prepared. Showing the original description.

Analyze failed launches, missed targets, or unsuccessful hires through a blameless review. Use five successive why questions to identify root causes, then record concrete changes with owners, deadlines, and ways to verify results.

• Investigating why a release was delayed
• Reviewing a missed sales or revenue target
• Examining a hiring decision that did not work out

Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.

• Review a production outage
• Investigate recurring defects
• Compare failing and working environments

Expert in running effective incident postmortems. Covers blameless analysis, root cause investigation, action item prioritization, and building a learning culture. Understands that incidents are opportunities to improve systems, not punish people. Use when "postmortem, incident review, what went wrong, root cause, blameless, outage, post-incident, " mentioned.

The English summary is being prepared. Showing the original description.

Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.

The English summary is being prepared. Showing the original description.

Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a production incident - even if they don't explicitly say "postmortem".

The English summary is being prepared. Showing the original description.

Investigate why a defect or insufficiency was introduced and accepted by tracing code, pull requests, task context, and accessible development sessions. Use for second-order learning after a fix, blameless root-cause analysis, or preventing a recurring class of engineering mistakes.

The English summary is being prepared. Showing the original description.

障害ふりかえり会議(blameless postmortem)。障害・トラブル・ミスの事後分析を、犯人探しではなく構造の改善につなげる会議として実行する。「ポストモーテム」「障害ふりかえり」「振り返り会議」「なぜ起きたか分析して」「再発防止を考えて」などのリクエストで使用。

The English summary is being prepared. Showing the original description.

Write incident review documents that focus on system conditions and learning. Organize timelines, examine root causes with evidence, and turn findings into practical follow-up actions with owners and deadlines, supported by a meeting facilitation guide.

• Writing a review after a service outage
• Analyzing root causes with the 5 Whys method
• Preparing an incident review meeting

Create a structured review after a production incident, focusing on systems and processes without blaming individuals. Reconstruct events, quantify impact, investigate causes, and document specific follow-up actions with named owners and deadlines.

• Write a review after a production outage
• Reconstruct an incident timeline from records
• Separate root causes from contributing factors

Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.

The English summary is being prepared. Showing the original description.

Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.

The English summary is being prepared. Showing the original description.

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.

The English summary is being prepared. Showing the original description.

Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.

The English summary is being prepared. Showing the original description.

Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produce corrective actions after an LLM failure. Produces a structured postmortem with trace reconstruction, a root-cause layer analysis, and corrective actions including a permanent regression case. For non-AI production incidents use incident-postmortem.

The English summary is being prepared. Showing the original description.

Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

The English summary is being prepared. Showing the original description.

Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning

The English summary is being prepared. Showing the original description.

Guide incident response from detection to post-mortem using SRE principles, severity classification, on-call management, blameless culture, and communication protocols. Use when setting up incident processes, designing escalation policies, or conducting post-mortems.

The English summary is being prepared. Showing the original description.

Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.

The English summary is being prepared. Showing the original description.

Write blameless incident postmortems with timeline reconstruction, root cause analysis, action items, and preventive measures

The English summary is being prepared. Showing the original description.

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality incident," "defect analysis," "improvement cycle." Not for: live release go/no-go decisions — use release-readiness. Not for ongoing metric dashboards — use qa-metrics. Not for reviewing existing test code quality — use ai-qa-review. Related: qa-metrics, test-reliability, test-strategy.

The English summary is being prepared. Showing the original description.