agentsclimarketplace

Amadeus incident response

Skill amadeus-dlc/amadeus/.agents/skills/amadeus-incident-response

Agent skills, templates, examples, validators, and docs for operating Amadeus DLC, a lifecycle contract for AI driven software development.

Install
npx -y skills add amadeus-dlc/amadeus --skill amadeus-incident-response

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the AI-DLC `incident-response` stage (operation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage incident-response --single`: the engine emits one run-stage directive for incident-response and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

SKILL.md

1.6 KB, as published. Nobody here has run it

AI-DLC Stage Runner — incident-response

Run the incident-response stage on its own. This is opt-in packaging over /amadeus --stage incident-response --single; the same stage is always reachable via that flag without this skill.

Steps

  1. Ask the engine for the single-stage directive:

    bun .codex/tools/amadeus-orchestrate.ts next --stage incident-response --single

    The engine emits one run-stage directive for incident-response (carrying the lead agent, the resolved consumes/produces paths, the rules and sensors in context, and — on this first directive — the conductor persona). Run the stage exactly as the directive describes; do not load the conductor persona by hand, the engine delivers it.

  2. When the stage's work is done, commit the single-stage record:

    bun .codex/tools/amadeus-orchestrate.ts report --single --stage incident-response --result completed

    This records a STAGE_STARTED / STAGE_COMPLETED pair under a synthetic workflow id and stops. It NEVER writes the main workflow's Current Stage — a single-stage run is isolated by design (the tool refuses to advance the main workflow).

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.