AAWEA.ORG

Manual start

↓

1

Read spec

Read spec.md. Pick the first unchecked requirement. Do not start multiple requirements in one pass.
2

Implement requirement

Implement that single requirement with tests. Mark it [x] in spec.md only after verification.
3

Verify

Run tests and manual checks listed in the spec for this requirement.

> npm test

↓

✓

Exit condition: manual

Every requirement in spec.md is checked off

📦 Install Files

These files are included when you download the loop.

📄 spec.md

# Feature spec

Check off each item only after it is implemented and verified.

## Requirements
- [ ] Requirement 1 — describe acceptance criteria
- [ ] Requirement 2 — describe acceptance criteria

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Read spec") S1("Implement requirement") S0 --> S1 S2("Verify") S1 --> S2 Exit{"Every requirement in spec.md is checked off"} S2 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Kickoff prompt

Start the "Spec-First Ship" loop.

Goal: every requirement in spec.md is implemented and checked off
Max iterations: 15
Between iterations run: npm test
Exit when: spec.md has no unchecked requirements

Step 1: Read spec.md, implement the first unchecked item, verify it, mark [x], and stop this iteration.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics