ADLC
Integrations

Claude Code

Adopt the ADLC inside Claude Code — phase-routing skill, gate commands, prosecutor subagent, and hooks that fire the gates automatically.

ADLC in Claude Code

Claude Code runs the whole lifecycle from inside the editor: a phase-routing skill, ticket/distill/maintain commands, a prosecutor subagent, and hooks that fire the gates automatically. No API keys — Claude is the model via --prompt-only.

Install

npx plugins add voodootikigod/adlc   # install the plugin into your agent tool(s)
npm install -g @adlc/cli             # the gate toolkit the plugin shells out to
/adlc-init                           # bootstrap .adlc/ in your repo (once)
npm install -g @adlc/cli
/plugin marketplace add voodootikigod/adlc
/plugin install adlc@adlc
/adlc-init

How each phase maps into Claude Code

ADLC phaseMechanismClaude Code vector
P0 Triage/adlc-ticketSlash command authors & triages a ticket into .adlc/tickets.json.
P1 Interrogateadlc spec-lint, parallaxPhase-routing skill runs the spec gates.
P2 Decomposeadlc coldstart, model-routerSkill resolves ticket scope and routes work by tier.
P3–P4 Rail & Buildadlc rails-guardHook blocks edits to frozen rails on every structured edit.
P5 Prosecuteprosecutor subagentFresh-context, refute-chartered review before merge.
P7 Distill/adlc-distillTurns repeated findings into deterministic defenses.

What gets installed

  • Skill: the adlc phase-routing skill that picks the right gate.
  • Commands: /adlc-init, /adlc-ticket, /adlc-distill, /adlc-maintain.
  • Subagent: adlc:prosecutor — the P5 pre-merge gate.
  • Hooks: structured-edit rails-guard + CI backstop.

Source: plugins/adlc-claude-code/.

Go deeper

The prosecution gate this integration automates: Prosecution, Not Code Review.

On this page