メニュー
Route software work through the Agentic Development Lifecycle in Cursor. Use when the user asks to apply ADLC, operate in ADLC, triage work, choose the next ADLC gate, or mentions P0–P7 / rails / prosecute.
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 |
| description | Route software work through the Agentic Development Lifecycle in Cursor. Use when the user asks to apply ADLC, operate in ADLC, triage work, choose the next ADLC gate, or mentions P0–P7 / rails / prosecute. |
Treat agentic development as phases with machine-checkable gates via
adlc <tool> (exit 0 = pass, 1 = operational error, 2 = gate fail).
Prerequisite: adlc --version works (npm i -g @adlc/cli). Run /adlc-init
or adlc init --harness cursor once per repo for the .adlc/ workspace.
Vague request, no ticket yet? ───────────────→ P0 /adlc-ticket
Have a spec / acceptance criteria? ──────────→ P1 /adlc-spec · /adlc-approve-spec
Have tickets, planning fan-out? ─────────────→ P2 /adlc-decompose
About to build, want to freeze tests? ───────→ P3 rails-guard hooks + CI
Mid-build / verify? ─────────────────────────→ P4 /adlc-verify-build
Change done, pre-merge prosecution? ─────────→ P5 /adlc-prosecute
Repeated review findings to bank? ───────────→ P7 /adlc-distill
Idle-time maintenance? ──────────────────────→ — /adlc-maintain
LLM-backed gates support --prompt-only: print the prompt, answer it yourself
in-session (no API keys). Prefer that over wiring providers.
Enforcement honesty: Cursor preToolUse deny is best-effort. The
unbypassable control is the CI rail-freeze gate (docs/ci/rails-guard.yml).
MCP tools (packaged): the plugin ships mcp.json → a lifecycle Roots
proxy (bin/adlc-mcp-wrapper.mjs) that spawns adlc mcp-server only after
resolving a consumer root. Tools: adlc_gate, adlc_prosecute. Requires
adlc on PATH (npm i -g @adlc/cli). Status until an installed-Cursor Roots
proof is recorded: wrapper landed / channel unverified — do not treat MCP
as production-shipped. Never guess process.cwd(); multi-root ambiguity fails
closed.
P5 caveat: prefer Task fan-out via packaged agents/prosecutor-* (fresh
context per lens). Sequential same-context is a degraded fallback with
weaker independence. For the cross-model risk gate run
npx adversarial-review --providers <a,b>.