Amadeus mvp

Skill amadeus-dlc/amadeus/.agents/skills/amadeus-mvp

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-mvp

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 workflow with the mvp scope baked in — no scope detection. Skip operations, ship the core. Packaging over `/amadeus --scope mvp`, which works without this skill.

SKILL.md

1.6 KB, as published. Nobody here has run it

AI-DLC — mvp scope

Drive the AI-DLC engine with the mvp scope fixed. This is the same deterministic forwarding loop the /amadeus orchestrator runs, with --scope mvp baked into the first next so scope detection is skipped. The engine owns all routing; the conductor persona arrives on the first directive's conductor_persona field — adopt it for the whole run.

The loop

directive = bun .codex/tools/amadeus-orchestrate.ts next --scope mvp $ARGUMENTS
Act on directive.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see amadeus-common/protocols/stage-protocol.md.
bun .codex/tools/amadeus-orchestrate.ts report --stage <directive.stage> --result <outcome> [--user-input "<text>"] when the directive names a stage; omit --stage only for non-stage report round-trips.
Treat the directive returned by the report as the next loop step. Continue immediately for run-stage, invoke-swarm, and print; stop for ask, select-intent, error, parked, or done.

Pass $ARGUMENTS through verbatim after --scope mvp; the engine parses any flags (--status, --stage, …) and the --scope from the state file always wins on an existing workflow, so re-running a started workflow resumes it. To run a different scope, use /amadeus --scope <other> instead.