adlc-spec
Run ADLC P0-P2 specification, interrogation, ticket decomposition, cold-start, merge forecast, and model routing workflows in Codex.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Run ADLC P0-P2 specification, interrogation, ticket decomposition, cold-start, merge forecast, and model routing workflows in Codex.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | adlc-spec |
| description | Run ADLC P0-P2 specification, interrogation, ticket decomposition, cold-start, merge forecast, and model routing workflows in Codex. |
ADLC_CODEX_SENTINEL_SPEC_V1
Drive P0-P2 with executable acceptance criteria.
Tickets are the contract every downstream ADLC tool reads (coldstart,
model-router, merge-forecast, rails-guard). Turn a request into a
well-formed, self-contained ticket through the canonical ticket store
service — never by hand-editing .adlc/tickets.json or shard files.
adlc ticket store status --json — confirm a store exists. If not, run
$adlc-init first; do not silently create the workspace here.adlc ticket list --json — inspect existing ids/hashes. If the interactive
command offers legacy migration, show the plan and honor the human's
answer; declining continues on legacy storage.A ticket must be executable without guesswork — exactly what coldstart
checks. Gather or infer:
T<n>; must be unique in the store.[].{ "to": "TX", "contract": "..." } lives on the prerequisite
ticket and means that ticket must complete before TX. If existing
tickets depend on the new one, add { "to": "<existing id>" } edges to the
new ticket. If the new ticket depends on an existing prerequisite T0,
the edge lives on T0, not the new ticket. Default [].duration defaults to
1 if unknown.If anything required for a self-contained ticket is ambiguous, ask rather
than guess — a vague ticket fails coldstart.
Write the proposed full ticket document to a temporary JSON file outside the
tracked store. Preview with adlc ticket create --input <file> --json
(dry-run by default) — review the plan, validation, graph effects, file
operations, and after-hash. Only once accepted, re-run with --write. Use
adlc ticket update <id> --input <file> --expect <ticketHash> --write for
edits to an existing ticket; a scope-widening or rail-narrowing edit
requires --authorize and becomes evidence-required (an audited, deliberate
change, not something to do casually). The service owns locking, full-graph
validation, compare-and-swap, journaling, and recovery — if it reports
RECOVERY_REQUIRED, stop and ask the human to choose
adlc ticket store recover --complete or --rollback. Never hand-edit the
store file, and never stage or commit the result yourself.
The atomic write just changed a tracked file. If the repo's formatter/linter
is not excluding .adlc/ (see $adlc-init), this can silently red the next
PR. Check for a scripts.check or scripts.lint entry in package.json;
run it scoped to the ticket file if the tool supports a path argument,
otherwise the full script. A failure here does not undo the write — warn
the human plainly and point them at $adlc-init's formatter-exclusion step.
coldstart is LLM-backed; inside Codex you are the model, so use the
prompt-only path — never the bare form, which needs an API key and exits 1
without one:
adlc coldstart <id> --prompt-only — prints the executability-audit
prompt and exits 0 without calling any provider.adlc parallax --request "<request>"
adlc spec-lint spec.md --json
adlc premortem spec.md --json
adlc coldstart --all --tickets .adlc/tickets.json --json
adlc merge-forecast --tickets .adlc/tickets.json --json
adlc model-router --tickets .adlc/tickets.json --json
Stop for human approval after P1 spec approval. Do not mark P2 complete until the ticket DAG and cold-start checks pass.