amadeus-feature

Route feature-scoped AI-DLC work through the orchestration loop using state-file driven directives.

5|Updated Jun 24, 2026

Search Tags:#orchestration #lifecycle #feature-scope #aidlc #stage-routing #grilling

Ready to run

npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amadeus-feature
Source: https://github.com/amadeus-dlc/amadeus/tree/main/.agents/skills/amadeus-feature
Command: npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need to manually choose or detect scope when running AI-DLC work for a feature, so the workflow starts in the right mode every time.

Core Features & Use Cases

Fixed Feature Scope: Runs the orchestration loop with feature scope baked in from the first directive.
Deterministic Routing: Follows the engine's run, ask, print, error, and done directives exactly as issued.
Workflow Continuation: Resumes existing feature work using the stored state instead of starting over.
Use Case: A developer can hand this Skill a feature request and let it drive the full AI-DLC sequence from intake through stage reporting and any grilling questions.

Quick Start

Ask the amadeus-feature skill to run your feature-scoped AI-DLC workflow and continue following its prompts until the work is complete.

Frequently Asked Questions about amadeus-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run feature-scoped AI-DLC workflows without manual scope detection?▼

Feature-scoped AI-DLC workflows can run without manual scope detection by using a routing loop that bakes the feature scope into the first directive and drives the full sequence from intake through stage reporting.

Can I resume an existing feature workflow from its saved state instead of starting over?▼

Yes, you can resume existing feature work by loading the stored state file, which allows the orchestration loop to continue the AI-DLC sequence exactly where it left off without restarting.

What is stage routing in AI-DLC and how does it handle ask directives?▼

Stage routing in AI-DLC follows deterministic engine directives—run, ask, print, error, and done—exactly as issued, routing grilling bridge responses back to the ask directives to maintain workflow continuity.

Does feature-scoped orchestration require setting the scope manually for each stage?▼

No, feature-scoped orchestration does not require manual scope setting per stage; the scope stays fixed from the initial directive, ensuring deterministic routing across stage-by-stage execution and resumed workflows.

When should I use a fixed feature scope for AI-DLC orchestration?▼

You should use a fixed feature scope for AI-DLC orchestration when handling new feature requests or executing stage-by-stage workflows where the feature boundary must remain unchanged throughout the entire lifecycle.

What are the limitations of state-file driven routing for feature workflows?▼

State-file driven routing for feature workflows is limited to deterministic directive handling and requires the feature scope to remain fixed; it cannot dynamically shift scope mid-execution or operate without the stored state file.