canon-incident

Create governed incident packets with blast radius and containment sequencing.

1|Updated Mar 26, 2026

Search Tags:#evidence #approvals #follow-up #containment #incident #packet #governed

Ready to run

npx skills add https://github.com/apply-the/canon --skill canon-incident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canon-incident
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-incident
Command: npx skills add https://github.com/apply-the/canon --skill canon-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal, auditable, governed incident packet workflow for outages and system incidents, ensuring blast-radius, containment sequencing, and follow-up readiness are captured and persisted.

Core Features & Use Cases

Expose the Canon incident workflow as a governed run started from your AI assistant.
Persist incident surface details including blast radius, containment steps, sequencing, and follow-up readiness for post-incident review.
Use Case: When an outage requires a formal, bounded incident packet to coordinate containment, evidence, and approvals.

Quick Start

Author a bounded incident brief at canon-input/incident/brief.md (or use an inline note) and invoke canon run --mode incident --system-context existing --risk <RISK> --zone <ZONE> [--owner <OWNER>].

Frequently Asked Questions about canon-incident

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a governed incident packet for outage containment?▼

A governed incident packet is a formal, auditable record that bounds blast radius, sequences containment actions, captures evidence, and logs approvals for post-incident review.

How do I create an auditable incident packet for a system outage?▼

Author an incident brief at canon-input/incident/brief.md, then invoke the Canon workflow with mode, system-context, risk level, and zone parameters to persist the formal incident record.

Can I use this incident workflow for existing system outages only?▼

Yes, this workflow applies specifically to incidents affecting existing systems where a formal, bounded, and auditable incident packet is required for containment coordination.

What risk and zone classifications are supported for incident containment?▼

The workflow supports risk classifications of low, bounded, or systemic, and zone classifications of green, yellow, or red to bound blast radius and guide containment sequencing.

Best way to persist incident evidence and follow-up readiness after an outage?▼

Use a governed incident packet workflow that captures containment steps, evidence, and approvals, then persists the complete record via Canon's incident workflow for post-incident review.

When do I need a formal incident packet for system containment?▼

You need a formal incident packet when an outage requires bounded blast radius coordination, containment sequencing, evidence capture, and formal approvals for auditable post-incident review.