Amadeus performance validation
Skill amadeus-dlc/amadeus/dist/kiro-ide/.kiro/skills/amadeus-performance-validation
Agent skills, templates, examples, validators, and docs for operating Amadeus DLC, a lifecycle contract for AI driven software development.
npx -y skills add amadeus-dlc/amadeus --skill amadeus-performance-validationAssembled 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 `performance-validation` stage (operation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage performance-validation --single`: the engine emits one run-stage directive for performance-validation 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.7 KB, 280 tokens by cl100k_base, as published. Nobody here has run it
AI-DLC Stage Runner — performance-validation
Run the performance-validation stage on its own. This is opt-in packaging over
/amadeus --stage performance-validation --single; the same stage is always reachable via
that flag without this skill.
Steps
-
Ask the engine for the single-stage directive:
bun .kiro/tools/amadeus-orchestrate.ts next --stage performance-validation --singleThe engine emits one
run-stagedirective forperformance-validation(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 .kiro/tools/amadeus-orchestrate.ts report --single --stage performance-validation --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).