About this project

AI-DLC (AI-Driven Development Life Cycle) is a harness-neutral, structured workflow framework designed to turn AI coding assistants into verifiable, auditable software delivery systems. It addresses the challenge of ad-hoc AI coding losing context as projects grow by keeping requirements, decisions, implementation, tests, and operational work connected through a standardized lifecycle. ### Key Features - **Lifecycle Structure:** Comprises 5 phases and 33 stages from initialization through operation. - **Agent Composition:** Employs 14 agents, including 11 domain experts, 2 reviewers, and an adaptive composer. - **Workflow Profiles:** Offers 11 workflow profiles for features, bug fixes, infrastructure, security, proofs of concept, enterprise delivery, and other common work. - **Governance:** Features human approval gates, source-bound review evidence, and a 99-event audit trail alongside persistent state, team knowledge, and learned rules. - **Deterministic Engine:** Provides a single consistent engine across all supported harnesses. ### Supported Harnesses The core engine runs natively across major AI coding environments, including: - Claude Code (invoked via `/aidlc`) - Kiro CLI and Kiro IDE - Codex CLI (invoked via `$aidlc`) - Cursor (invoked via `/aidlc` or `agent`) - opencode (invoked via `/aidlc`) - GitHub Copilot CLI / VS Code (invoked via `/aidlc`) ### Installation and Configuration Users can install AI-DLC via a native installer for macOS, Linux, WSL, or Windows PowerShell, which adds the `aidlc` command and all harness runtimes without requiring Bun or Node.js. Alternatively, users can manually copy the `runtime/<harness>/` directory into their project using Bun. Project setup is handled by running `aidlc config --harness <name>` followed by `aidlc doctor` to verify the environment. Model provider setup is handled by the respective harness, with Amazon Bedrock as the default for Claude Code and shipped Codex configurations, and the methodology itself remains provider-independent. ### Repository Structure - `core/`: Contains the hand-authored, harness-neutral methodology, engine, and 71 authoring tools. - `harness/<name>/`: Holds thin, harness-specific manifests and integrations. - `plugins/<name>/`: Houses optional AIDLC plugins. - `scripts/`: Contains packaging, binary, installer, and release tooling. - `tests/`: Includes smoke, unit, integration, and end-to-end test suites. - `docs/`: Provides user guides, harness engineering docs, and developer references.