Amadeus approval handoff

Skill amadeus-dlc/amadeus/dist/claude/.claude/skills/amadeus-approval-handoff

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-approval-handoff

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 `approval-handoff` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage approval-handoff --single`: the engine emits one run-stage directive for approval-handoff 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, 286 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC Stage Runner — approval-handoff

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

Steps

Ask the engine for the single-stage directive:
```
bun .claude/tools/amadeus-orchestrate.ts next --stage approval-handoff --single
```
The engine emits one run-stage directive for approval-handoff (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 .claude/tools/amadeus-orchestrate.ts report --single --stage approval-handoff --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 agent orchestration skills give in 286 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06

run the full test suite after integrating changesin 53 of 742, across 20 files
reference existing artifacts by path or URLin 52 of 742, across 22 files
dispatch one agent per independent problem domainin 50 of 742, across 17 files
verify fixes do not conflictin 45 of 742, across 13 files
include a suggested skills section in the documentin 45 of 742, across 15 files
redact sensitive informationin 41 of 742, across 11 files
save to the temporary directory of the operating systemin 39 of 742, across 9 files
tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
spot check agent changes for systematic errorsin 34 of 742, across 7 files
write a handoff document summarising the current conversationin 31 of 742, across 6 files
assign each agent a specific scopein 23 of 742, across 8 files
provide specific scope and clear goalin 23 of 742, across 5 files

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 stage work is done

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.