Menú
Run ADLC P3-P4 rail and build workflows in Pi, including frozen rails, hollow-test, rails-guard, preflight, and flail detection.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | adlc-rail-build |
| description | Run ADLC P3-P4 rail and build workflows in Pi, including frozen rails, hollow-test, rails-guard, preflight, and flail detection. |
P3 rails are authored before P4 build and are frozen during P4.
The Pi adlc-pi-extension automatically intercepts and enforces rail-freeze and suppression-marker rules! Ensure that you have the active ticket set:
export ADLC_TICKET=<ticket-id>
Or make sure .adlc/current-ticket.json is set to your current ticket.
Required gates and checks:
adlc hollow-test --test-cmd "npm test"
adlc preflight --test-cmd "npm test" --json
adlc rails-guard --ticket "$ADLC_TICKET" --tickets .adlc/tickets.json --record --json
adlc flail-detector session.log --json
Inside Pi, prefer the native adlc_gate tool (e.g. adlc_gate({gate: "rails-guard", args: "--ticket $ADLC_TICKET --tickets .adlc/tickets.json"})) over shelling these adlc <gate> commands — it enforces the rails-aware argv policy and records gate evidence automatically; the CLI shown above stays the fallback for gates it denies (write/derived-target gates and --*cmd invocations).
Hooks are assistive. adlc rails-guard is the deterministic rail-freeze proof.
Routes agentic development work to the right Agentic Development Lifecycle (ADLC) gate. Use when shaping a spec or ticket, deciding how to fan out work to models, protecting frozen rails during a build, prosecuting a change before merge, or distilling repeated review findings into defenses. Triggers on "shape this spec", "is this ticket ready", "freeze these tests", "prosecute this change", "is this safe to merge", "ADLC", "which gate", "spec-lint", "premortem", "coldstart", "rails-guard", "hollow-test", "behavior-diff".
Prosecute a change before merge (ADLC P5) — prove the tests are load-bearing rather than hollow, make behavior change visible, measure whether review would actually catch a planted defect, and record revision-bound evidence. Use before merging, or on requests like "prosecute this change", "is this safe to merge", "are these tests real", "will review catch anything".
Bootstrap the ADLC runtime in a repository — install the gate toolkit, create the .adlc/ workspace, and wire the CI rails-guard control. Use when adopting the Agentic Development Lifecycle in a repo for the first time, when `adlc --version` fails, when `.adlc/` is missing, or on requests like "set up ADLC here", "install ADLC", "initialize the lifecycle".
Routes agentic development work to the right Agentic Development Lifecycle (ADLC) gate. Use when shaping a spec or ticket, deciding how to fan out work to models, protecting frozen rails during a build, prosecuting a change before merge, or distilling repeated review findings into defenses. Triggers on "shape this spec", "is this ticket ready", "freeze these tests", "prosecute this change", "is this safe to merge", "ADLC", "which gate", "spec-lint", "premortem", "coldstart", "rails-guard", "hollow-test", "behavior-diff".
Refute-charter review discipline for prosecuting a diff against its ticket. Use when asked to act as a prosecutor, reviewer, or to find reasons a change must not merge.
Run ADLC P7 distillation and maintenance workflows in Codex, including lesson-foundry, rejection-mining, skill-mining, scheduled maintenance, skill-rot, model-ratchet, review-calibration, and gate-fuzzing.