Aidlc Mvp

Run the AI-DLC workflow with the mvp scope baked in — no scope detection. Skip operations, ship the core. Packaging over `/aidlc --scope mvp`, which works without this skill.

aws-samples 74c80be 1.4 KB Updated

File contents

AI-DLC — mvp scope

Drive the AI-DLC engine with the mvp scope fixed. This is the same deterministic forwarding loop the /aidlc orchestrator runs, with --scope mvp baked into the first next so scope detection is skipped. The engine owns all routing; the conductor persona arrives on the first directive's conductor_persona field — adopt it for the whole run.

The loop

  1. directive = bun .kiro/tools/aidlc-orchestrate.ts next --scope mvp $ARGUMENTS
  2. Act on directive.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see aidlc-common/protocols/stage-protocol.md.
  3. bun .kiro/tools/aidlc-orchestrate.ts report --stage <directive.stage> --result <outcome> [--user-input "<text>"] when the directive names a stage; omit --stage only for non-stage report round-trips.
  4. Repeat from step 1 until directive.kind == done.

Pass $ARGUMENTS through verbatim after --scope mvp; the engine parses any flags (--status, --stage, --test-run, …) and the --scope from the state file always wins on an existing workflow, so re-running a started workflow resumes it. To run a different scope, use /aidlc --scope <other> instead.

aws-samples/sample-ai-sales-roleplay/tree/main/.kiro/kiro-ide/.kiro/skills/aidlc-mvp commit 74c80be2c9

Frequently asked questions

npx skillmds@latest add aws-samples/aidlc-mvp