agentsclimarketplace

Amadeus init

Skill amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-init

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

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

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.

SKILL.md

2.2 KB, 460 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

  1. 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-birth reads the description from the --arguments flag, 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 --arguments text is preserved separately in the audit + state. Omit --label only when there is no description (the tool then falls back to the scope token):

    bun .codex/tools/amadeus-utility.ts intent-birth --scope <name> --arguments "<description>" --label "<2-3 word essence>"
    

    --scope seeds the initial scope (defaults to poc); omit --arguments and --label when the user gave no description. Print the tool's output and stop. This does not advance a stage; run /amadeus afterwards to continue.

Gives 0 of the 12 instructions most project setup skills give in 460 tokens

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

  • Ask one question at a timein 29 of 999, across 28 files
  • Detect the package manager from lockfilesin 28 of 999, across 9 files
  • Present findings to the userin 26 of 999, across 5 files
  • Explore current repo statein 24 of 999, across 3 files
  • Update the agent skills block in place if it existsin 24 of 999, across 3 files
  • Install husky lint-staged and prettierin 23 of 999, across 4 files
  • Create the lintstagedrc filein 22 of 999, across 3 files
  • Commit all changed filesin 22 of 999, across 3 files
  • Run lint-staged to verify it worksin 22 of 999, across 3 files
  • Create the husky pre-commit filein 21 of 999, across 2 files
  • Create a prettierrc file if missingin 21 of 999, across 2 files
  • Initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

  • birth the intent
  • forward recognized flags as-is
  • pass freeform description via arguments flag
  • derive a short kebab-case label from arguments
  • omit label when no description is provided
  • run amadeus afterwards to continue

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.