Menu
Initialize or refresh an ADLC repository for Codex. Use for first-time ADLC setup, requests to bootstrap `.adlc/`, install project-scoped ADLC subagents, or repair missing Codex repository configuration.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | adlc-init |
| description | Initialize or refresh an ADLC repository for Codex. Use for first-time ADLC setup, requests to bootstrap `.adlc/`, install project-scoped ADLC subagents, or repair missing Codex repository configuration. |
adlc init --help to confirm the installed CLI contains the initializer.
If it does not, stop and direct the user to the source-checkout command in the
Codex integration guide; do not imply that an older registry release has it.adlc init --json from the repository root.created, updated, unchanged, and warnings fields..adlc/config.json, .adlc/specs/, and the three
.codex/agents/adlc-*.toml profiles exist.adlc preflight --json and report any failed readiness check.The initializer is idempotent and preserves project-owned files. Never edit or copy
files into ~/.codex; Codex project agents belong under the repository's
.codex/agents/ directory.
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.