amadeus-incident-response

Run the isolated incident-response stage without advancing the main workflow.

5|Updated Jun 24, 2026

Search Tags:#orchestration #incident response #ai-dlc #workflow isolation #stage runner #synthetic workflow

Ready to run

npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-incident-response

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you run the AI-DLC incident-response stage by itself when you need a focused operation-phase pass without changing the main workflow state.

Core Features & Use Cases

Single-stage execution: Runs only the incident-response stage and its gate as an isolated workflow.
Workflow safety: Commits a synthetic start/completion record while leaving the main workflow's Current Stage untouched.
User-guided interaction: Supports grilling-style question handling so users can answer one question at a time during the stage.
Use case: Use it when you need to recover, validate, or complete an incident-response task without advancing any other AI-DLC stage.

Quick Start

Ask the AI to run the isolated incident-response stage for the current task and follow the prompts until the single-stage run is completed.

Frequently Asked Questions about amadeus-incident-response

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

FAQPage Schema

How do I run an isolated incident response stage without advancing the main workflow?▼

To run an isolated incident response stage without advancing the main workflow, you execute the single stage as a synthetic workflow. This commits a synthetic start and completion record while preserving the main workflow's Current Stage untouched.

What is workflow isolation for AI-DLC incident handling?▼

Workflow isolation for AI-DLC incident handling is a mechanism that executes a single incident response stage independently. It allows focused operation-phase passes for recovery or validation without changing the overarching AI-DLC workflow state.

Can I handle user questions one at a time during an incident response workflow?▼

Yes, you can handle user questions one at a time during an incident response workflow. The isolated stage runner supports grilling-style question handling, allowing users to answer prompts individually until the single-stage run is completed.

When should I use a synthetic workflow for incident response?▼

You should use a synthetic workflow for incident response when you need a focused operation-phase pass for recovery, targeted validation, or completing an incident task. It ensures the main workflow state remains unchanged during isolated execution.

Does running a recovery stage affect the main workflow's current stage?▼

No, running a recovery stage does not affect the main workflow's current stage. The isolated execution commits synthetic reporting records for the incident response stage while explicitly preserving the main workflow's Current Stage.

What is the best way to validate an incident response task without moving to the next AI-DLC phase?▼

The best way to validate an incident response task without moving to the next AI-DLC phase is running an isolated stage execution. This performs focused validation within a synthetic workflow, leaving the main workflow state untouched.