incident-command-governor
Build governed incident command packets. Use when asked to standardize incident review, run severity assessment, or assemble incident communication.
- License 许可
- MIT
- 最近更新
- 2026-09-23
- Stars
- ★ 8
- Forks
- 2
01 前言 Front Matter
- name
- incident-command-governor
- description
- Build governed incident command packets. Use when asked to standardize incident review, run severity assessment, or assemble incident communication.
02 资源文件 12
- 参考文档agents/interface.yaml411 B
- 参考文档evals/trigger_cases.json522 B
- 参考文档input/incident_input_example.json613 B
- 参考文档manifest.json539 B
- 参考文档outputs/incident_packet_example.md815 B
- 参考文档references/comms-policy.md336 B
- 参考文档references/review-policy.md397 B
- 参考文档references/severity-matrix.md332 B
- 参考文档reports/context_budget.json416 B
- 参考文档reports/governance_score.json772 B
- 参考文档reports/revision_history.md163 B
- 脚本scripts/build_incident_packet.py1.1 KB
03 SKILL.md 正文
Incident Command Governor
When To Use
- You need a reusable incident command packet from messy operational inputs.
- You need explicit severity assessment, stakeholder updates, and action ownership.
- You need a governed workflow that can be reviewed, maintained, and audited over time.
Do Not Use
- The task is only to explain an incident concept.
- The task is only to draft a one-off update.
- The request is still brainstorming and not yet packaging a repeatable incident workflow.
Workflow
- Gather the minimum incident inputs:
- incident summary
- timeline evidence
- affected systems and customers
- severity indicators
- owners and responders
- stakeholder audiences
- Read
references/severity-matrix.mdto assign or confirm severity. - Read
references/comms-policy.mdto shape internal and external updates. - Read
references/review-policy.mdbefore finalizing, because this skill is maintained under a monthly review cadence. - Use
scripts/build_incident_packet.pywithinput/incident_input_example.jsonwhen deterministic packet assembly is needed. - Produce one governed incident packet with:
- incident summary
- severity block
- evidence-backed timeline
- affected scope
- owner and action table
- internal and external comms blocks
- explicit open risks and review notes
- Stop and report blockers if severity evidence or ownership data is missing.
Output Contract
The final answer must include:
- a concise incident summary
- explicit severity and rationale
- a timeline section
- impact scope
- owners and next actions
- stakeholder communication blocks
- governance note for follow-up review
Validation Checklist
- Severity is justified with evidence, not guessed.
- Owner and next actions are explicit.
- Communications are separated by audience.
- Missing evidence is surfaced as a blocker.
- The packet can be reviewed again without reconstructing context from chat history.
Reference Map
- Read
references/severity-matrix.mdfor severity rules. - Read
references/comms-policy.mdfor communication guidance. - Read
references/review-policy.mdfor review cadence and governed lifecycle expectations. - Inspect
evals/trigger_cases.jsonfor routing boundaries. - Inspect
outputs/incident_packet_example.mdfor an example final artifact. - Inspect
reports/governance_score.jsonfor the current maturity snapshot.
04 同仓库更多 Skills
broken-yaml-skill
Broken YAML fixture for packager failure testing.
invalid-governance-skill
Test fixture for governance validation.
frontend-review
Review frontend code for accessibility, UI security, missing states, and UX regressions. Use when asked to review React components, run a pre-merge frontend review, or check a11y and unsafe rendering.
note-cleanup
Clean messy meeting notes into structured markdown summaries. Use when asked to organize meeting notes, extract action items, separate decisions from open questions, or turn rough notes into a clean recap.
frontend-review
Review frontend code for accessibility, risky UI security issues, missing loading and error states, and pre-merge regressions. Use when asked to review React, UI, forms, frontend components, or merge-readiness for the frontend.
frontend-review
Review frontend code before merge.