Amadeus deployment pipeline

Skill amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-deployment-pipeline

Run the AI-DLC `deployment-pipeline` stage (operation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage deployment-pipeline --single`: the engine emits one run-stage directive for deployment-pipeline 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.From its SKILL.md

Install

npx -y skills add amadeus-dlc/amadeus --skill amadeus-deployment-pipeline

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.

SKILL.md

1.7 KB, 286 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC Stage Runner — deployment-pipeline

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

Steps

Ask the engine for the single-stage directive:
```
bun .codex/tools/amadeus-orchestrate.ts next --stage deployment-pipeline --single
```
The engine emits one run-stage directive for deployment-pipeline (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.
When the stage's work is done, commit the single-stage record:
```
bun .codex/tools/amadeus-orchestrate.ts report --single --stage deployment-pipeline --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).

Gives 0 of the 12 instructions most ship operate skills give in 286 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

ask the engine for the single-stage directive
run the stage exactly as the directive describes
commit the single-stage record when done