| name | aidlc-build-and-test |
| generated-by | aidlc-runner-gen |
| description | Run the AI-DLC `build-and-test` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage build-and-test --single`: the engine emits one run-stage directive for build-and-test 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.
|
| argument-hint | |
| user-invocable | true |
AI-DLC Stage Runner — build-and-test
Run the build-and-test stage on its own. This is opt-in packaging over
/aidlc --stage build-and-test --single; the same stage is always reachable via
that flag without this skill.
Steps
-
Ask the engine for the single-stage directive:
bun .codex/tools/aidlc-orchestrate.ts next --stage build-and-test --single
The engine emits one run-stage directive for build-and-test (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 .codex/tools/aidlc-orchestrate.ts report --single --stage build-and-test --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).