skills.rest
amadeus-dlc
amadeus-dlcOFFICIAL
Explore all skills by this author →
GitHub

amadeus-mvp

Execute fixed-scope MVP runs of the AI-DLC lifecycle with state-file-driven routing.

5|Updated Jun 24, 2026
Search Tags:#automation#workflow#orchestration#mvp#intake#ai-dlc#stage-routing
One-click install
npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-mvp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amadeus-mvp
Source: https://github.com/amadeus-dlc/amadeus/tree/main/.agents/skills/amadeus-mvp
Command: npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-mvp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It runs the AI-DLC workflow with the mvp scope fixed, removing the need for scope detection and helping teams execute a lightweight lifecycle path for a focused product slice.

Core Features & Use Cases

  • Fixed mvp scope from the first orchestration step so reruns resume deterministically.
  • Routes work through the AI-DLC loop by handling run-stage, ask, print, error, and done directives.
  • Supports stage reporting and user-input handoffs for mvp intents, scope-locked continuations, and one-path shipping workflows.

Quick Start

Use the amadeus-mvp skill to execute the AI-DLC loop for an mvp-scoped intent and follow each directive until the run completes.

Frequently Asked Questions about amadeus-mvp

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

FAQPage Schema
How do I automate a fixed-scope MVP workflow for AI-assisted software development?▼

To automate fixed-scope MVP workflows, you can run the AI-DLC lifecycle with the scope locked from the first orchestration step, removing the need for scope detection and enabling deterministic reruns.

How does deterministic stage routing work for an MVP intent without scope detection?▼

Deterministic stage routing for an MVP intent works by using state-file-driven routing alongside the amadeus orchestrator to handle run-stage, ask, print, error, and done directives automatically.

What is the best way to resume an MVP scope-baked rerun during an AI-DLC loop?▼

The best way to resume a scope-baked rerun is to use state-file-driven routing within the fixed MVP execution path, ensuring the lifecycle resumes exactly where it left off deterministically.

Do I need the amadeus orchestrator to handle AI-DLC intake continuation and reporting?▼

Yes, you need the amadeus orchestrator and stage-protocol handling to execute intake continuation, manage stage reporting, and process user-input handoffs within the AI-DLC loop.

Can I use state-file-driven routing for one-path shipping workflows in AI-DLC?▼

Yes, state-file-driven routing supports one-path shipping workflows by applying fixed-scope MVP execution to route work through the AI-DLC loop until the run completes.

When should I avoid fixed-scope MVP execution for AI-assisted software development?▼

You should avoid fixed-scope MVP execution if your project requires dynamic scope detection or flexible stage routing outside the deterministic one-path lifecycle provided by the amadeus orchestrator.

Related Skills

Explore More Software Engineering Skills→
googlegoogle
731

mantis-pipeline-adapter

Design deterministic orchestrator harnesses for security review pipelines.

Official
Advanced
amadeus-dlcamadeus-dlc
5

amadeus-feature

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

Official
Advanced
amadeus-dlcamadeus-dlc
5

amadeus-bugfix

Run the AI-DLC bugfix workflow for a specific defect without scope detection.

Official
Advanced
Shak-ZhuShak-Zhu
2

pm-ai-delivery-control

Manage project lifecycles, requirements, scope, work packages, and stage closures.

Community
Advanced