39 个 · 按相关度排序
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
Document an incident with a sourced timeline, clear user impact, and analysis that separates symptoms, triggers, and underlying causes. Produce a blameless review with action items that specify responsible teams, deadlines, and checkable completion criteria.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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".
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
障害ふりかえり会議(blameless postmortem)。障害・トラブル・ミスの事後分析を、犯人探しではなく構造の改善につなげる会議として実行する。「ポストモーテム」「障害ふりかえり」「振り返り会議」「なぜ起きたか分析して」「再発防止を考えて」などのリクエストで使用。
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示英语简介。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Write blameless incident postmortems with timeline reconstruction, root cause analysis, action items, and preventive measures
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。