post-emergency-review

Evaluate emergency decisions against pre-authorized scopes using structured review templates.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/JadeZaher/neos-operating-system --skill post-emergency-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-emergency-review
Source: https://github.com/JadeZaher/neos-operating-system/tree/main/neos-core/layer-08-emergency/post-emergency-review
Command: npx skills add https://github.com/JadeZaher/neos-operating-system --skill post-emergency-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents the informal expansion of emergency authority by mandating a structured, independent review of every emergency decision against its pre-authorized scope, ensuring accountability and preventing scope creep over time.

Core Features & Use Cases

  • Independent Review: Conducts retrospectives with a body that excludes anyone who held emergency authority.
  • Scope-Based Evaluation: Assesses each decision against its pre-authorized scope, not just its outcome.
  • Use Case: After a critical system outage, this Skill ensures a thorough review of all emergency actions taken, identifying any decisions that exceeded their authorized limits, thereby strengthening future crisis response protocols.

Quick Start

Initiate a post-emergency review for the recent 'system-outage-2024-07-15' event.

Frequently Asked Questions about post-emergency-review

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

FAQPage Schema
How do I conduct a post-emergency review for crisis response accountability?

A post-emergency review evaluates crisis decisions against pre-authorized scopes by examining crisis logs and reversion records. It requires an independent body, excluding those who held emergency authority, to use structured review templates and checklists for comprehensive analysis and recommendation generation.

What is emergency authority scope creep and how does a retrospective prevent it?

Emergency authority scope creep is the informal expansion of powers during a crisis. A mandatory retrospective prevents this accretion by independently evaluating every emergency reversion against its pre-authorization registry, ensuring accountability and confirming actions did not exceed authorized limits.

When do I need a mandatory emergency retrospective for governance and risk management?

You need a mandatory emergency retrospective after any critical system outage or emergency reversion. It ensures governance by examining crisis logs and reversion records through structured review templates, verifying that all crisis response actions aligned with pre-authorized scopes.

Can I use structured checklists to evaluate emergency reversions against pre-authorization registries?

Yes, structured review templates and checklists are required to evaluate emergency reversions against pre-authorization registries. This process examines crisis logs and reversion records to identify any decisions that exceeded authorized limits, strengthening future crisis response protocols.

Does an independent post-emergency review exclude personnel who held emergency authority?

Yes, an independent post-emergency review must exclude anyone who held emergency authority during the crisis. This separation ensures unbiased accountability when evaluating decisions, crisis logs, and reversion records against pre-authorized scopes.

What limitations exist when relying on crisis logs for emergency review analysis?

Emergency review analysis requires comprehensive crisis logs, reversion records, and pre-authorization registries. Limitations arise if these records are incomplete, as the structured review templates depend on examining full documentation to identify decisions that exceeded authorized limits and generate accurate recommendations.