AAWEA.ORG

Manual start

↓

1

Run build

Run the project build command and capture all errors.

> npm run build
2

Fix build errors

Fix compile, type, and bundling errors one at a time. Prefer minimal diffs.
3

Re-run build

Run the build again and confirm errors are resolved.

> npm run build

↓

✓

Exit condition: tests_pass

Production build completes with exit code 0

> npm run build

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Run build") S1("Fix build errors") S0 --> S1 S2("Re-run build") S1 --> S2 Exit{"Production build completes with exit code 0"} 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

Run "Build Until Green" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "Build Until Green" loop.

Goal: production build succeeds
Max iterations: 10
Between iterations run: npm run build
Exit when: npm run build exits 0

Step 1: Run the build. If it fails, fix the first error, then repeat until green.

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