Godiva Severity Rules

Classify Godiva service incidents by severity and enforce role-based approval gates.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/myriosMin/godiva --skill godiva-severity-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Godiva Severity Rules
Source: https://github.com/myriosMin/godiva/tree/main/claude-managed-agents/skills/godiva-severity-rules
Command: npx skills add https://github.com/myriosMin/godiva --skill godiva-severity-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes how Godiva service incidents are classified and approved, reducing delays and miscommunication during incident response.

Core Features & Use Cases

  • Severity classification rules for Critical, Major, and Minor incidents
  • Defined approval gates with role-based sign-offs and escalation timing
  • Blast radius guidance to avoid wide-impact changes and ensure safe actions
  • Alignment with runbooks and SOPs to streamline cross-functional decision making

Quick Start

Configure the severity rules and approval gates to govern incident response in your Godiva deployment.

Frequently Asked Questions about Godiva Severity Rules

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

FAQPage Schema
How do I classify Godiva service incidents by severity level?▼

Classify Godiva service incidents by severity using defined rules for Critical, Major, and Minor incidents. The classification guides execution gates, blast radius awareness, and role-based sign-offs to standardize incident response.

What is the approval workflow for a Critical incident on the Godiva platform?▼

The approval workflow for a Critical Godiva incident enforces role-based sign-offs with explicit escalation timing. This governance ensures timely approvals and reduces miscommunication during high-severity incident response.

How do I configure severity rules and approval gates for incident governance?▼

Configure severity rules and approval gates by defining role-based sign-offs and escalation timing for Critical, Major, and Minor incidents. This setup governs incident response and enforces blast radius awareness across your deployment.

When do I need blast radius guidance during incident response?▼

Blast radius guidance is needed during incident response to avoid wide-impact changes and ensure safe actions. It aligns with runbooks and SOPs to streamline cross-functional decision making within the Godiva platform.

Can I align these severity rules with existing runbooks and SOPs?▼

Yes, the severity rules align with existing runbooks and SOPs to streamline cross-functional decision making. This alignment standardizes incident classification and approval workflows, reducing delays during Godiva incident response.

Why does incident classification need role-based execution gates?▼

Incident classification needs role-based execution gates to enforce timely approvals and prevent unauthorized actions. Defined gates with explicit escalation timing standardize response and reduce miscommunication across Godiva service incidents.