Who it is forAn engineering team where people use different AI coding tools but the delivery process has to be the same for audits and reviews.
The problemEach tool gets its own prompts and rules, so the process differs by person and reviewers cannot compare work.
The outcomeOne deterministic engine behind every supported harness, with the same phases, approvals and audit trail in each tool.
What you need first
- macOS, Linux, WSL or Windows PowerShell
- A supported coding agent
Steps
- Install AI-DLC on each machine; on Windows use
irm https://github.com/awslabs/aidlc-workflows/releases/latest/download/install.ps1 | iexin a normal PowerShell window - Each person configures their tool, for example
aidlc config --harness codexoraidlc config --harness cursor - Kiro IDE users run
aidlc config --harness kiro-ide; Copilot users useaidlc config --harness copilot - Everyone runs
aidlc doctorfrom the project root - Start workflows with /aidlc, or $aidlc in Codex CLI
- After version upgrades finish the active workflow, then run aidlc config again to avoid skew
Prompt for your agent
Configure awslabs/aidlc-workflows in this repo for <my harness> and run aidlc doctor. Then compare the harness table in the README with what my teammates use (<tools>) and list any version minimums we do not meet.
Caveat. Each harness has a minimum version, for example Codex CLI 0.145.0 and opencode 1.17.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for awslabs/aidlc-workflows and "Use one workflow across Claude Code, Kiro, Codex and Copilot"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer