Enforce pipeline progression rules — hard gates require user approval, soft gates auto-proceed on success. Use whenever a pipeline stage has a gate annotation.
The backbone skill that enforces progression control across all pipelines.
When a stage is annotated with a hard gate:
| Response | Action |
|---|---|
approved / yes / lgtm / proceed | Continue to next stage |
| Feedback text (anything else substantive) | Redo the stage incorporating feedback |
skip | Log the skip with a warning, advance to next stage |
abort | Terminate the pipeline, preserve all artifacts produced so far |
When a stage is annotated with a soft gate:
Track the following state throughout pipeline execution:
feature, bugfix, refactor).pending, in-progress, passed, failed, skipped.When any failure occurs during pipeline execution:
FAILURE.md file documenting what failed, at which stage, and with what error.