· How it works
From ticket to merged PR every step gated.
The same five phase pipeline runs whether you hand tOOrunt AI a one line product idea or a ticket off your existing backlog. A human decides three things; everything else runs inside the gates.
- phases
- 5
- gates cleared
- 14
- your signatures
- 3
- cycle
- hours
From idea to shipped software
04Idea → shipped software · humans decide three things
- IdeaThe same five phase pipeline runs whether you hand tOOrunt AI a one line product idea or a ticket off your existing backlog.
- HUMANPRD signedIt posts an implementation plan to Jira: files, approach, risks, and acceptance criteria, then stops. It never writes code before a human sees the plan.
- BacklogIt watches your board, picks up the ticket, and resolves the right GitHub repo from a curated registry or a semantic match. Ambiguous requirements get a clarifying question, never a guess.
- Build + testsIt implements the change and writes tests until green. For a bug, it writes a reproduction test that is RED before the fix and GREEN after. This proves the fix actually fixes the bug.
- Peer reviewA second agent reviews a seven point checklist; a peer bot with a distinct identity reviews the PR. Human comments are handled one by one: fixed, politely rebutted, or asked about.
- HUMANPR approveA peer bot with its own GitHub identity reviews the change in a real, adversarial pass, then waits for your approval before the second gate opens.
- HUMANMerge + watchIt merges only on verified green tests, CI, no conflicts, and review approval, then watches CI and production, raising a revert alert if the change regresses.
3 human decisions: sign the PRD, approve the PR, unlock the merge · 14 hard gates on every change · everything between them runs autonomous, on the record
01The pipeline
Five phases. Each one clears its gates or stops.
- 01
Ingest & scope
It watches your board, picks up the ticket, and resolves the right GitHub repo from a curated registry or a semantic match. Ambiguous requirements get a clarifying question, never a guess.
01 right repo02 requirements03 dependencies
- 02
Plan & approval gatehuman
It posts an implementation plan to Jira: files, approach, risks, and acceptance criteria, then stops. It never writes code before a human sees the plan.
04 plan approved (human gate)05 novelty
- 03
Implement & prove
It implements the change and writes tests until green. For a bug, it writes a reproduction test that is RED before the fix and GREEN after. This proves the fix actually fixes the bug.
06 rework07 tests green08 quality09 coverage10 no secrets
- 04
Review orchestrationhuman
A second agent reviews a seven point checklist; a peer bot with a distinct identity reviews the PR. Human comments are handled one by one: fixed, politely rebutted, or asked about.
11 risk cap12 review signed (human gate)
- 05
Merge & watchhuman
It merges only on verified green tests, CI, no conflicts, and review approval, then watches CI and production, raising a revert alert if the change regresses.
13 merged (human gate)14 watched
- ∞
Continuous learning
Every reviewer correction becomes a lesson and a graduated guardrail. The next ticket starts smarter and the improvement is on the dashboard.
02The surfaces
Where you watch it actually happen.
One bot per teammate
Every action has an owner.
Per bot Jira and GitHub identities, with least privilege tokens scoping each bot to its repos. A peer bot with its own GitHub identity reviews the change in a real, adversarial pass, so review is bot to bot and it gates the merge.
- identity
- jira + github, per bot
- token scope
- least privilege
- review
- bot to bot, gates merge
03Your seat
Three decisions. All yours, only yours.
Sign the PRD
The plan waits in Jira until you reply /approve or /reject with a reason it has to answer. In auto with veto mode this becomes a timed window: it proceeds unless you object.
Approve the PR
By the time it reaches you, a peer bot with its own GitHub identity has already torn the change apart once. Your review is the second signature, not the first line of defense.
Unlock the merge
The merge button only arms on verified green: tests, CI, zero conflicts, review approval. Your click is the last gate and the watch that follows it is automatic.
04Review
It answers review like an engineer, not a bot.
Every comment gets one of four honest responses: fix it, disagree with a reason, ask when the intent is unclear, or refuse when it’s unsafe. The last one is the point.
This N+1 query will hammer the DB under load. Batch it.
Good catch. Batched into a single `IN (...)` fetch and added a covering test that fails on the old code path.
Watch it answer review on your own repo.
Book a demo05Autonomy
You choose how much rope. It’s a config, not a rebuild.
Start with a human on every plan and PR. Earn your way to full autonomy as the track record builds. The envelope widens on post merge evidence and snaps back on a single regression.
Every plan and PR waits for you.
The agent posts a plan to Jira and stops until a human replies /approve. Maximum control, the day one posture for a new team.
- Gate 04 · plan
- you sign
- Gate 12 · review
- you sign
- Gate 13 · merge
- you sign
06The fleet
Ten bots, zero collisions.
- Atomic claims
- A ticket is claimed exactly once. Two bots can race for it, one wins, and the other moves on.
- File claim locks
- Every bot declares the files it will touch before it starts; overlapping claims queue instead of colliding.
- Park & failover
- Blocked on a dependency, a bot parks the ticket with its state intact. Any peer can resume it from the record.
- Escalation ladder
- Who to contact is deterministic: CODEOWNERS, git blame, Jira roles, and on call. The ladder is bounded, so it always terminates.
Get started
Point it at your backlog. See it ship.
A live demo on a repo you choose.