Describe an outcome.It ships the PR.
Operator surveys your repo, drafts a parallel plan, fans the work across isolated microVMs, runs tests, and opens a reviewable pull request — without being babysit.
Reads before it acts.
Before writing a line, Operator maps your project — conventions, test suite, existing modules, migration history. Changes land where they belong.
One task, four branches.
Operator decomposes the request into parallel tracks — each running in its own VM, each inspectable before it merges.
schema
Reads current Prisma schema, drafts migration for the new billing table, generates rollback.
interface
Builds the React billing dashboard, wires Stripe webhook handler, adds loading + error states.
billing
Implements checkout session, subscription lifecycle, and invoice retrieval against test mode.
tests
Writes integration tests for every new route. Runs them on a clean VM with seeded test data.
All four lanes at once.
Each branch gets its own microVM. They run in parallel, report back live, and hand off to tests automatically. Merge order resolves itself.
One PR. Every change.
Operator merges the passing branches, writes a summary, and opens a reviewable PR with a preview link. You decide whether to merge.
You only approved the outcome.