메뉴
Incident management from detection through postmortem. USE WHEN incident, outage, SEV1, SEV2, production down, postmortem, blameless review, incident response, war room, incident update, status page, root cause analysis, 5 whys, incident timeline, on-call.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/mj-deving/pai-skills --skill incident명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | Incident |
| description | Incident management from detection through postmortem. USE WHEN incident, outage, SEV1, SEV2, production down, postmortem, blameless review, incident response, war room, incident update, status page, root cause analysis, 5 whys, incident timeline, on-call. |
Manage incidents across 4 phases: Triage → Communicate → Mitigate → Postmortem.
Before executing, check for user customizations at:
${PAI_USER_DIR}/SKILLCUSTOMIZATIONS/Incident/
If this directory exists, load and apply:
PREFERENCES.md - Severity thresholds, escalation contacts, communication templatesThese define user-specific preferences. If the directory does not exist, proceed with skill defaults.
| Workflow | Trigger | File |
|---|---|---|
| New | "new incident", "production down", "SEV1" | Workflows/New.md |
| Update | "incident update", "status update" | Workflows/Update.md |
| Postmortem | "postmortem", "blameless review", "root cause" | Workflows/Postmortem.md |
Example 1: Start a new incident
User: "Production API is returning 500s for all users"
→ Invokes New workflow
→ Assesses severity, identifies affected systems
→ Produces triage summary + status update + communication draft
Example 2: Post a status update
User: "Update the incident — we identified the cause, it's a bad deploy"
→ Invokes Update workflow
→ Structures update with current status, actions taken, next steps
→ Outputs formatted status update ready to post
Example 3: Write postmortem
User: "Write the postmortem for yesterday's outage"
→ Invokes Postmortem workflow
→ Reconstructs timeline, runs 5 Whys analysis
→ Produces blameless postmortem with action items
Severity Levels:
| Level | Criteria | Response Time |
|---|---|---|
| SEV1 | Total outage, all users affected | Immediate, all-hands |
| SEV2 | Major degradation, many users affected | < 15 min, on-call team |
| SEV3 | Partial degradation, some users affected | < 1 hour, assigned team |
| SEV4 | Minor issue, workaround available | Next business day |
Phases: