Agile Iteration Method — v1.6

AI work that stays
scoped and reviewable

AIM is a way to run agentic software delivery without losing the thread. It gives AI work a clear loop instead of a prompt spiral.

PO TDO Dev Reviewer TDO PO

Why AIM

Without a method, agentic development usually breaks in predictable ways:

🔄
The agent jumps between theories without proving anything.
📈
Scope expands silently while work keeps piling up.
📁
“Progress” becomes partial edits instead of a shippable slice.
No one knows what the next approval actually means.

AIM fixes that with clear roles, gates and ownership.

The loop

Roles are played in sequence for each Done Increment. The loop repeats until the Epic is complete.

PO

Owns the Epic. Defines value, scope, non-goals and acceptance criteria. Decides when the Epic is complete.

TDO

Translates the Epic into one concrete Done Increment. Limits scope. Validates the increment after review.

Dev

Implements exactly one Done Increment. Focus is on end-to-end value, not partial work.

Reviewer

Reviews for correctness, edge cases and technical risk. Provides concrete, actionable feedback.

Approval gates

Approvals only matter at three points. Everything else is signal, not permission.

Gate A — Epic

PO frames the Epic. Scope and value boundary agreed.

Gate B — Increment

TDO proposes the next single Done Increment. PO approves or adjusts scope.

Gates C & D — Soft

Dev and Reviewer report progress and risk. No approval needed unless escalation occurs.

Gate E — Acceptance

TDO presents the completed increment. PO accepts or requests adjustment.

Get started

Choose one path:

Fast start command

/aim start "EPIC: <desired user outcome>"
Mode: Strict
Cost profile: Cost Control

Use Cost Control for ordinary low-risk work. Use Deep when the work touches trust, data correctness, deployment, migration, security, or public APIs.

Strict vs Auto

Mode: Strict

Pauses at the meaningful hard gates. Default for new teams or high-trust-sensitive work.

Mode: Auto

Continues through increments automatically unless an escalation condition is hit. Same gate logic, faster throughput.

Choose your adapter

AIM works with the tools you already use. The method stays the same across all of them.

GitHub Copilot

Use the packaged aim agent in .github/agents/. Add .github/prompts/ for Copilot-style command helpers.

/aim start "EPIC: …"

Claude Code

Use CLAUDE.md plus the shipped starter files in .claude/commands/ and .claude/agents/.

EPIC: … / Mode: Strict

Codex

The repo is the AIM contract. The Codex skill adds the /aim launcher plus bootstrap help.

/aim start "EPIC: …"

Important: .github/agents/aim*.agent.md are part of the AIM instruction layer, not just Copilot decoration. Install them regardless of which adapter you use.

Cost profiles

Cost profile controls runtime depth, not approval flow. Gates and escalation rules are the same regardless of which profile you choose.

Standard

Normal AIM with progressive context loading and compact gates. The default for most work.

Cost Control

For low-risk, reversible cleanup or narrow documentation changes. Escalates to Standard or Deep when risk appears.

Deep

For trust-sensitive, data correctness, deployment, migration, security, or public API work. Broader inspection, stronger review.

Cost Control is not weaker AIM. It is AIM with a smaller runtime budget and a clear rule to escalate when risk appears.

The fastest way to get agentic value

1
Copy the core AIM files

Add AGENTS.md, docs/workflow/agile-iteration-method.md, and .github/agents/aim*.agent.md to the target repo.

2
Add /.aim to .gitignore

The .aim/ folder is runtime state. AIM creates it automatically on first start.

3
Make AGENTS.md repo-aware

Add your stack, verification strategy, and deployment constraints. Vague rules produce vague behavior.

4
Start your first Epic
EPIC: <desired user outcome>
Mode: Strict
Cost profile: Cost Control

For the full installation guide: docs/workflow/install-aim-1.6.md

Docs