「incident」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

IR playbook execution, evidence collection, forensic timeline analysis, memory forensics, and post-incident reporting following NIST SP 800-61 and SANS PICERL methodology

日本語の概要は準備中です。原文の説明を表示しています。

Construction safety incident reporting and analysis. Capture incidents, conduct investigations, track corrective actions, and analyze trends for prevention.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a comprehensive breach response team playbook defining CSIRT and privacy team structure with named roles (incident commander, legal counsel, communications, IT forensics, DPO), escalation matrices, communication templates, pre-negotiated vendor contacts, and regulatory authority contacts organized by jurisdiction. Keywords: breach response playbook, CSIRT, incident response team, escalation matrix, communication templates, vendor contacts.

日本語の概要は準備中です。原文の説明を表示しています。

Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and manage production incidents. Trigger with "we have an incident", "production is down", "something is broken", "there's an outage", "SEV1", or when the user describes a production issue needing immediate response.

日本語の概要は準備中です。原文の説明を表示しています。

Create operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Triggers on requests to create runbooks, document procedures, or when user asks "how do we handle incidents?", "runbook", "operational procedures", "on-call guide", "incident response", "maintenance procedures". Outputs RUN- entries with step-by-step operational procedures.

日本語の概要は準備中です。原文の説明を表示しています。

When things go wrong - and they will - how you communicate determines whether you lose customers for a day or lose trust forever. Crisis communications isn't about spin or damage control. It's about being human when your company is at its most vulnerable. This skill covers incident response communications, public apologies, data breach notifications, service outages, PR crises, and the aftermath. The goal isn't to look good - it's to be good, and communicate that clearly. Use when "crisis, incident, outage, down, breach, apology, we messed up, customers are angry, PR disaster, viral complaint, status page, postmortem, trust recovery, bad press, crisis, incident, communications, apology, trust, status-page, outage, breach, postmortem, recovery" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.

日本語の概要は準備中です。原文の説明を表示しています。

Coordinates an active production incident by establishing command, reducing blast radius, preserving evidence, communicating verified impact, restoring service, validating recovery, and creating owned follow-up actions. Use for outages, severe degradation, security or data-integrity events, failed releases, and urgent operational triage. Not for a normal local bug, routine alert tuning, or a postmortem after the incident is already closed.

日本語の概要は準備中です。原文の説明を表示しています。

Guides incident response from detection through postmortem. Use when designing on-call runbooks, triaging production incidents, writing status updates, or improving MTTD and MTTR.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate incident response — triage, root cause, remediate, prevent recurrence. USE WHEN active alerts, data broken, stale, pipeline failure, or investigate and fix a data incident.

日本語の概要は準備中です。原文の説明を表示しています。

Use when identifying cybersecurity-specific regulations and incident reporting obligations. Covers NIS2, DORA, SEC cyber disclosure rules, CISA incident reporting, state breach notification laws, cyber insurance requirements, and security certification frameworks. USE FOR: NIS2, DORA, SEC cybersecurity rules, CISA, breach notification, incident reporting, SOC 2, ISO 27001, cyber insurance, FedRAMP, StateRAMP, CMMC, data breach response DO NOT USE FOR: implementing security controls (use security skills), security testing tools (use security/security-testing), general data privacy (use privacy-data-protection)

日本語の概要は準備中です。原文の説明を表示しています。

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Design incident response for AI system failures. TRIGGERS - Use when user needs help with ai-incident-response related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Write blameless incident postmortems following Google SRE methodology. Covers timeline reconstruction, root cause analysis (5 Whys), impact assessment, and action items with owners. Use after production incidents, outages, or significant bugs to prevent recurrence.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer User Support Specialist — triaging an inbound ticket's severity and SLA clock before troubleshooting it, verifying a caller's identity before any password/MFA/account-state change, walking a live incident through a structured troubleshooting sequence instead of guessing at a fix, deciding whether a request is an incident, a service request, or the underlying problem behind a string of incidents, or judging whether a ticket should resolve at tier 1 or genuinely needs escalation.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a workplace safety incident tracking system for incident classification accuracy, root cause analysis depth, OSHA 300 log recordkeeping compliance, trend analysis capabilities, and leading indicator identification..

日本語の概要は準備中です。原文の説明を表示しています。

Analyze an incident response program for playbook coverage, MTTR optimization opportunities, evidence collection readiness, root cause analysis quality, and post-incident review effectiveness. Triggers: building a SOC, assessing IR maturity, optimizing detection-to-recovery timelines.

日本語の概要は準備中です。原文の説明を表示しています。

Summarizes cybersecurity breach incidents into structured legal and compliance records. Trigger when synthesizing incident reports, forensics, logs, or notifications into a defensible chronology, scope-impact analysis, response ledger, or regulatory-risk assessment. Keywords: data breach, incident response, unauthorized access, ransomware, exfiltration, GDPR, CCPA, HIPAA.

日本語の概要は準備中です。原文の説明を表示しています。

Decision-making patterns in incident command and emergency management leadership contexts

日本語の概要は準備中です。原文の説明を表示しています。

The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)

日本語の概要は準備中です。原文の説明を表示しています。

Responds to phishing incidents by analyzing reported emails, extracting indicators, assessing credential compromise, quarantining malicious messages across the organization, and remediating affected accounts. Covers email header analysis, URL/attachment sandboxing, and mailbox-wide purge operations. Activates for requests involving phishing response, email incident, credential phishing, spear phishing investigation, or phishing remediation.

日本語の概要は準備中です。原文の説明を表示しています。