Your backlog, worked as pull requests you merge.

1. "Users find the bugs before we do." Each bug becomes a ticket, and the fix a pull request your CI checks before you see it.
2. "The migration has been next quarter for a year." We break it into small tickets, each one a pull request you can read in one sitting.
3. "We'll split the monolith one day." Same method: one small, reviewable step at a time, never one giant branch.
4. "Every week goes to firefighting." The backlog keeps moving while your team handles the fire.
5. "I can't say where the engineering hours go." Every piece of work is an issue and a pull request in your repository, so the record is in GitHub, where you already look.

1. A one-line ticket. You, or your own Claude, write what you want as an issue on your board.
2. A plan as small tickets. A planner breaks it into small issues, each small enough to review.
3. A normal pull request. A developer agent writes the change on a branch and opens a pull request, like anyone on your team. Your CI runs on it.
4. QA by a different model. A reviewer on another model checks the change against the ticket and the checks. A pass from the model that wrote it is refused.
5. You press merge. The pull request waits for you. Nothing reaches your main branch until you merge it.

On our own repositories, a pull request takes a median of 19 minutes from opened to merged, and about 4 in 5 pass QA first time.

That is review-to-merge pipeline time, not the wait in a backlog. We give a date for your work after scoping it.

1. Agents get tasks, never a token that can write. An agent is handed a ticket and submits its work to our governor. At most it gets a short-lived, read-only token to check out the code. Only the governor writes to GitHub, as an App you installed, on the one repository you chose.
2. A different model reviews pull requests. The governor refuses a pass from the model that wrote the change, and the review names both models. On our own repositories, 94% of governed pull requests were reviewed by a second agent on a different model.
3. Every write is re-checked and logged. The governor re-checks each submission against the live repository before it writes anything, and records each action in its audit log. In GitHub, every change shows as the App's.
4. You own the merge. By default the merge is yours, in your repository. We merge only if you ask us to, and that is a recorded decision.
5. Uninstall the App to pull the plug. Remove our Apps in your GitHub settings. New access stops; a token already issued expires within the hour. Merged work stays in your repository.

"Different model" means a different model id, not a different vendor.