Requirements in.
Working features out.
Describe a feature. Agents plan against your real code, build, review, fix, and attach screenshot proof for every acceptance criterion. You approve the plan and merge the PR. It's how Turbodiff builds itself.
Anyone can generate code. We ship proof. · open source · MIT-licensedAnyone can generate code.
We ship proof.
Turbodiff's own commit history is the pitch. Every merged feature carries its plan, its checks, and a screenshot per acceptance criterion.
Four lights. One PR.
Every task on the board shows where it is at a glance. The same four stages run on every feature, and you step in twice: to approve the plan, and to merge.
Agents read your real repo, not a summary, and write a plan with files, acceptance criteria and risks.
you approve →A sandbox on the edge checks out a branch, implements the plan, runs your checks, and opens the PR.
agents workA reviewer agent reads the diff and fixes what it finds. Then the app is launched and every criterion gets a screenshot.
proof attachedYou review the plan, diff, checks, and agent findings, then decide whether to merge.
you merge →