governance-incident-response

Coordinate production-incident response with severity classification and post-mortem documentation.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-incident-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-incident-response
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/governance-incident-response_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-incident-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a structured, auditable workflow for production incidents to minimize downtime and ensure evidence-based remediation across on-call teams.

Core Features & Use Cases

  • Severity classification (P0-P3) and impact isolation
  • Root-cause investigation and evidence-based remediation
  • Structured fix or rollback workflows with approvals
  • Clear status communication and post-mortem documentation
  • Standardized outputs such as incident registry and post-mortem reports

Quick Start

Create a new incident record in Documentation/Incidents/INC-YYYY-NNN and follow the defined steps to classify, isolate, investigate, remediate, and post-mortem.

Frequently Asked Questions about governance-incident-response

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

FAQPage Schema
How do I coordinate structured production incident response to minimize downtime?

Structured production incident response minimizes downtime by guiding on-call teams through triage, severity classification, root-cause analysis, fix or rollback, and post-mortem documentation. It enforces auditable incident logging and standardized resolution workflows.

What is the best way to classify incident severity during a service disruption?

Incident severity classification uses a P0-P3 scale to isolate impact during a service disruption. This mechanism prioritizes outages, performance degradations, and security events to direct remediation efforts and standardize response protocols.

How do I conduct a root-cause investigation for an outage with documented rollback plans?

Root-cause investigation for an outage requires validated evidence-based analysis paired with structured fix or rollback workflows. It enforces documented rollback plans with approvals to ensure safe remediation and prevent recurring service disruptions.

When do I need standardized post-mortem documentation for production incidents?

Standardized post-mortem documentation for production incidents is needed after resolving outages or security events. It ensures auditable resolution by generating an incident registry and post-mortem reports in the Documentation/Incidents directory.

Can I use this structured incident response workflow for performance degradations and security events?

This structured incident response workflow applies across outages, performance degradations, security events, and service disruptions. It coordinates triage and remediation to ensure evidence-based resolution and standardized post-mortem outputs.

Why does incident response require enforced incident logging and severity classification?

Incident response requires enforced incident logging and severity classification to ensure evidence-based remediation and auditable resolution. It standardizes impact isolation and validates root-cause investigation across on-call teams.