Dev Loop

Setup

Do this only once per repo. Ensure the .agents/ folder is ignored in the repo (for example, add .agents/ to .gitignore)

Usage

User will ask you to run dev.loop. This is usually with either an existing design spec or a stated goal.

If user gives you an existing spec - go straight to step 2 (Gather Context). Otherwise, start at step 1 (Plan).

If the task is straightforward, you can skip creating a spec and go straight to step 3.

If the user asks you to "check in after creating the spec" or uses similar wording, treat that as a pause point before implementation, not as permission to skip the immediate post-spec gather-context work. Unless the user explicitly says to stop before review, still complete the required spec review, ambiguity/gap analysis, and recommendation fold-in from step 2 before checking in.

In addition to running the whole dev.loop, users can also invoke an individual phase of the dev.loop by referring to it (eg. re-run the "verify" phase)

Whenever practical - use one or more subagents to run any given phase to preserve context