2.0 KiB
name, generated-by, description, argument-hint, user-invocable
| name | generated-by | description | argument-hint | user-invocable |
|---|---|---|---|---|
| aidlc-observability-setup | aidlc-runner-gen | Run the AI-DLC `observability-setup` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage observability-setup --single`: the engine emits one run-stage directive for observability-setup 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. | true |
AI-DLC Stage Runner — observability-setup
Run the observability-setup stage on its own. This is opt-in packaging over
/aidlc --stage observability-setup --single; the same stage is always reachable via
that flag without this skill.
Steps
-
Ask the engine for the single-stage directive:
aidlc engine orchestrate next --stage observability-setup --singleThe engine emits one
run-stagedirective forobservability-setup(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. -
Before acting on the directive, read
.aidlc/aidlc-common/protocols/stage-protocol.md. Then read every.aidlc/aidlc-common/protocols/stage-protocol-<module>.mdnamed bydirective.protocol_modules. Load every listed module before reading the stage body or running its topology; skip only a module already loaded earlier in this session. -
When the stage's work is done, commit the single-stage record:
aidlc engine orchestrate report --single --stage observability-setup --result completedThis 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).