adlc

Route software work through ADLC gates P1-P7 using Codex CLIs.

16|2|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/voodootikigod/adlc --skill adlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adlc
Source: https://github.com/voodootikigod/adlc/tree/main/plugins/adlc-codex/skills/adlc
Command: npx skills add https://github.com/voodootikigod/adlc --skill adlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route software work through the Agentic Development Lifecycle in Codex to ensure gate-based progress and reduce human error.

Core Features & Use Cases

  • Deterministic gating: classify work into trivial, bounded, substantial, or architectural phases.
  • Guided command flow: instructs the user on which ADLC CLI to run.
  • Triage and gating: helps triage tasks and select the appropriate next gate.
  • Use Case: When a user asks to apply ADLC or operate in ADLC, the skill recommends commands and phase choices.

Quick Start

Run adlc preflight --json to validate gates, then execute the desired phase with adlc run <p1|p2|p3|p4|p5|p6|p7> and the required flags.

Frequently Asked Questions about adlc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Agentic Development Lifecycle for routing software work?

The Agentic Development Lifecycle (ADLC) is a gate-based workflow that routes software work through deterministic phases using Codex. It classifies work into trivial, bounded, substantial, or architectural phases to reduce human error and enforce progress validation.

How do I triage software tasks and select the next ADLC gate?

To triage software tasks and select the next ADLC gate, run the ADLC skill to classify your work and recommend the appropriate phase command. You execute the desired phase using adlc run <p1-p7> with the required flags.

How do I validate ADLC gate completion using command line tools?

You validate ADLC gate completion by running the adlc preflight --json command. This deterministic CLI checks your progress and requires .adlc/manifest.jsonl evidence to validate that the current gate is fully satisfied.

Does the Agentic Development Lifecycle require specific evidence files to pass gates?

Yes, the Agentic Development Lifecycle requires a .adlc/manifest.jsonl evidence file to validate gate completion. The deterministic ADLC CLIs enforce pass/fail criteria based on this manifest to ensure gate-based progress.

What are the limitations of deterministic gating in the ADLC workflow?

Deterministic gating in the ADLC workflow requires strict adherence to the .adlc/manifest.jsonl evidence format and specific CLI commands. Without proper manifest evidence, the deterministic pass/fail CLIs will not validate your gate completion.

When do I need gate-based progress validation for software engineering tasks?

You need gate-based progress validation when operating within the ADLC workflow across phases P1-P7. It is required when you must triage tasks into trivial, bounded, substantial, or architectural categories and enforce deterministic completion checks.