From idea to production, with receipts.

Install into the repo you are already in

cd /path/to/your/repo
npx aisdlc-cli init

This writes the skills into your harness's skill directories, a docs/ process tree, and an aisdlc.json marker. Claude Code users can instead install the plugin: /plugin marketplace add AnshRoshan/aisdlc, then /plugin install aisdlc@aisdlc for the skills plus /aisdlc-next and /aisdlc-status commands.

Open a feature with a lane

npx aisdlc-cli new "Payment retries" --kind backend

Pick a lane: spike (a question), quick (bounded change), standard (new capability), regulated (money, PII, auth). The lane decides which gates apply, and only moves up.

Talk to your agent

use aisdlc-brainstorm, I want to build payment retries

The brainstorm skill classifies the work, interviews you with recommended answers, and routes to aisdlc-discover → aisdlc-spec. The spec is EARS-format; you sign §5. No one signs it for you.

Let the gates referee

npx aisdlc-cli next payment-retries --json

Every stage ends with this. It reads the files, derives the state, names the blocking items and the one skill to load next. The agent obeys the disk, not the chat.

Approve as a human

npx aisdlc-cli approve G1 payment-retries
refused: you authored plan.md

Approvals are bound to the hash of the artifact. Edit the plan afterwards and the approval goes stale, and the CLI sends the state backwards. Agents can never approve; the approver can never be the author.

Verify, don't trust

npx aisdlc-cli verify payment-retries -- npm test
… 41 passed (41), exit 0, 8.2s
evidence/20260906T154412-full.json recorded

aisdlc verify runs the command itself and records a hash-chained evidence file. "Tests pass" without a recorded run is not a state the process accepts.

The full command set