Ship specs through code review
Run spec-driven workflow loop every 10 minutes: plan work, collect reviews, execute tasks, open pull requests.
/loop 10m /flow-next:pilot # build loop: ready spec → plan → reviews → work → draft PR Cap the run at 15 passes.
claude-code · codex
Source: gmickel ↗graded C · 70/100 — how grades work →
More ci loops
Get the build green
Run the build, fix the first error, and repeat until npm run build exits 0, with a 10-turn cap.
/goal `npm run build` exits 0 — run the build, fix the first error, repeat until it succeeds; stop after 10 turns
cilow risk
Get the build green, every time
Work through each task in .toh/plan.md, fix blockers, until the build command succeeds or you hit 40 turns.
/goal every task in .toh/plan.md is checked and the build command exits 0 — or stop after 40 turns . A Haiku evaluator judges the condition FROM THE TRANSCRIPT — one more reason the QC gate quotes actual output: unquoted results are invisible to the evaluator. |
cimedium risk
Get lint and E2E tests passing
Execute work from PLAN.md until npm run lint and npm run test:e2e pass, scoping changes per AGENTS.md.
/goal Implement the work described in PLAN.md. Stop only when npm run lint and npm run test:e2e pass. Follow AGENTS.md, keep changes scoped, and report verification evidence Stop after 25 turns even if the goal is not reached.
cimedium risk