Amadeus application design
Skill amadeus-dlc/amadeus/.agents/skills/amadeus-application-design
Run the AI-DLC `application-design` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage application-design --single`: the engine emits one run-stage directive for application-design 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
npx -y skills add amadeus-dlc/amadeus --skill amadeus-application-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things 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.
- runs commandsInstructs the agent to run 2 commands, including `bun .codex/tools/amadeus-orchestrate.ts next --stage application-design --single` and 1 more.
SKILL.md
1.7 KB, 280 tokens by cl100k_base, as published. Nobody here has run it
AI-DLC Stage Runner — application-design
Run the application-design stage on its own. This is opt-in packaging over
/amadeus --stage application-design --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 application-design --singleThe engine emits one
run-stagedirective forapplication-design(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 application-design --result completedThis 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).