One idea in.
Write it the way you would brief a colleague: what to change, what must stay the same, and how to test it. The run on this page is an example.
ronin start "Let people export a notebook as a PDF from the share menu." --repo notes-app
Three lines from the example brief
- Use the existing share sheet. No new screens.
- The PDF must match what is on screen, images included.
- Test it on a 200-page notebook: export must finish in under ten seconds.
Code runs the stages.Models do the work.
Each role runs on its own model. Here design is skipped, because the brief said to use the existing share sheet.
branch ronin/20261015-091204
example run
- 01setupwaitingrunningdone
- 02hookswaitingrunningdone
- 03mapwaitingrunningdone
- 04productwaitingrunningdone
- 05specwaitingrunningdone
- 06designwaitingrunningskipped
- 07backendwaitingrunningdone
- 08frontendwaitingrunningdone
- 09qawaitingrunningneeds you
- 10reviewwaitingrunningnext
Red means you.
It stops for a question only you can answer, a spent budget, the same issue raised three times, or a problem it cannot assign.
The example run’s first half hour
- 09:12humansetupKickoff: should export include notes shared with you?
- 09:31bouncefrontend“Export button does nothing on tablets,” raised 3 times.
- 09:36unsureqaImages missing from the PDF. Owner unclear: backend or frontend.
- 09:44humanqaQA needs a test account with a 200-page notebook to finish.
What Ronin checks
Every tool call.
Checked before it runs. Secrets in .env are never read, and shell commands must be on the role’s list.
Every ticked task.
Must come with changed files, or it is not done.
Every coder round.
Ends with the repo’s own build and tests for that layer.
Every button.
Gets tapped in the running app. One that does nothing goes back to frontend.
Start a run.
ronin start "<idea>" --repo <path>It runs on your own machine, with Claude Code, Codex or OpenCode doing the work.