Amadeus init
Start an AI-DLC workflow — run the whole Initialization phase (mint the intent, detect the workspace, build state) in one step, without typing a stage. The engine normally auto-births the first intent; this is opt-in packaging over that move. Pass `--scope <name>` to seed the initial scope (defaults to poc), or a freeform description of what to build.From its SKILL.md
npx -y skills add amadeus-dlc/amadeus --skill amadeus-initAssembled 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
2.2 KB, 461 tokens by cl100k_base, as published. Nobody here has run it
AI-DLC — start a workflow (birth the first intent)
Start a fresh AI-DLC workflow. The workspace shell ships in dist/ (no setup
command), and the engine auto-births the first intent when you describe what to
build — this skill is opt-in packaging over that birth move. Initialization is a
PHASE, not a single stage — it mints the intent, detects the workspace
(greenfield/brownfield), and builds amadeus-state.md together, in one
deterministic call. There is no per-init-stage runner because an init stage has
no standalone meaning.
Steps
-
Birth the intent (run the initialization phase). Parse the user's
$ARGUMENTS: forward any recognized flags (--scope <name>/--depth <level>/--test-strategy <level>) as-is, and pass any freeform description text via--arguments "<text>"(intent-birthreads the description from the--argumentsflag, NOT a positional — forwarding it bare would silently drop it). ALSO derive a short--label: a 2-3 word kebab-case essence of what's being built ("I would like to build a simple calculator application"→--label "simple calc"). The label becomes the readable, date-prefixed record dir name (<YYMMDD>-simple-calc); the full--argumentstext is preserved separately in the audit + state. Omit--labelonly when there is no description (the tool then falls back to the scope token):bun .kimi-code/tools/amadeus-utility.ts intent-birth --scope <name> --arguments "<description>" --label "<2-3 word essence>"--scopeseeds the initial scope (defaults topoc); omit--argumentsand--labelwhen the user gave no description. Print the tool's output and stop. This does not advance a stage; run/amadeusafterwards to continue.