Aidlc Scope Definition

Run the AI-DLC `scope-definition` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage scope-definition --single`: the engine emits one run-stage directive for scope-definition 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.

aws-samples b613add 1.6 KB Updated

File contents

AI-DLC Stage Runner — scope-definition

Run the scope-definition stage on its own. This is opt-in packaging over /aidlc --stage scope-definition --single; the same stage is always reachable via that flag without this skill.

Steps

  1. Ask the engine for the single-stage directive:

    bun .kiro/tools/aidlc-orchestrate.ts next --stage scope-definition --single
    

    The engine emits one run-stage directive for scope-definition (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.

  2. When the stage's work is done, commit the single-stage record:

    bun .kiro/tools/aidlc-orchestrate.ts report --single --stage scope-definition --result completed
    

    This 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).

aws-samples/sample-ai-sales-roleplay/tree/main/.kiro/kiro-ide/.kiro/skills/aidlc-scope-definition commit b613add230

Frequently asked questions

npx skillmds@latest add aws-samples/aidlc-scope-definition