Menu
Run ADLC P3-P4 rail and build workflows in Codex, including frozen rails, hollow-test, rails-guard, preflight, flail detection, and the context-fitness build gate.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | adlc-rail-build |
| description | Run ADLC P3-P4 rail and build workflows in Codex, including frozen rails, hollow-test, rails-guard, preflight, flail detection, and the context-fitness build gate. |
ADLC_CODEX_SENTINEL_RAIL_BUILD_V1
P3 rails are authored before P4 build and are frozen during P4. Initialize the
project with $adlc-init, then select the ticket through the normal ADLC ticket
workflow. The native Codex hook automatically arms when
.adlc/current-ticket.json selects an incomplete ticket with non-empty rails.
Use ADLC_P4_ENFORCEMENT=1 only to force enforcement in automation or unusual
shell workflows. Use ADLC_P4_ENFORCEMENT=0 only as a deliberate local opt-out;
it does not bypass the authoritative CI gate. ADLC_TICKET remains an explicit
selection override when no current-ticket file is present.
A second PreToolUse hook, adlc-build-gate.mjs, guards against continuing a
high-blast-radius build in a context-rotted session. It only applies to
tickets whose risk tier is 'high' (declared risk: 'high', an
external-system effect, identity mutation, or scope/rails touching the
manifest or ticket-store trust root, or category contract/architecture) —
a normal-risk ticket is never gated. For a high-risk ticket, the hook reads
the session transcript (transcript_path on the hook payload) and denies the
next mutating tool call once the session looks context-degraded (more than 40
tool calls in a bounded window, or a transcript past 256 KiB). It does not
gate a fresh or shallow session, even a high-risk one.
If you hit this gate: resume in a fresh session (or an isolated subagent)
rather than continuing in a degraded one — that is the fix, not the bypass.
To override deliberately, set ADLC_BUILD_GATE_BYPASS=1; the override is
refused unless it durably records to the gate-manifest
(adlc gate-manifest record build-gate-bypass), so an unaudited bypass is
never silently honored.
Required gates:
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
Hooks are immediate guardrails. adlc rails-guard and the required CI job are
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.