newspaper_wedding/.aidlc/skills/aidlc-ci-pipeline/SKILL.md

name, generated-by, description, argument-hint, user-invocable

name	generated-by	description	argument-hint	user-invocable
aidlc-ci-pipeline	aidlc-runner-gen	Run the AI-DLC `ci-pipeline` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage ci-pipeline --single`: the engine emits one run-stage directive for ci-pipeline 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 — ci-pipeline

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

Steps

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

   aidlc engine orchestrate next --stage ci-pipeline --single
   

   The engine emits one run-stage directive for ci-pipeline (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. Before acting on the directive, read .aidlc/aidlc-common/protocols/stage-protocol.md. Then read every .aidlc/aidlc-common/protocols/stage-protocol-<module>.md named by directive.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.

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

   aidlc engine orchestrate report --single --stage ci-pipeline --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).