AIDD Workflow
Four commands. One loop. A version you can trust.
You name the outcome. AIDDbot writes the spec, builds the change, and ships it with proof.
Specs before code, so the agent does not invent. Rules in the repo, so the code follows your standards. A second agent checks the work, so you verify instead of hope.
Four commands
| You get | Command | |
|---|---|---|
| Start | A map of the system and the rules the agent will follow | /architect-initial-foundation |
| Draft | A spec you approve now and build when you are ready | /architect-requested-spec |
| Ship | One change, proved and released | /build-requested-spec |
| Repair | Debt cleared, quality that lasts | /craft-lasting-quality |
Architect designs. Builder writes the code and the tests. Craftsman proves the change and ships. The reviewer is never the author.
In Codex, start each command with $.
In the repository
Gates, drafts, and debt: How it works · AIDD workflow
Next: Get started · GitHub