Tagout takes an idea to a merged pull request while you do something else. Say what you want; your coding agent files the issue with a plan, builds it on a branch, opens the pull request, waits for CI and merges it. Every step is checked by a script that stops the agent when something is wrong and says what to fix.
No green tag, no merge.
tagouttagout-migrate/migrate pipeline to verified production. Needs RoselineMCP (.NET 10 SDK). The .NET add-on.Refusal, as written by the gatehooks/git-write-gate.sh
git-write-gate.shgit commit, the raw commandguarded-commit.sh -C <worktree> <branch> -- <git commit args>One issue of this repository, from the idea to the merge. Its pull request was opened at 12:07:43 and merged at 12:24:27, 17 min later. The three links are the proof.
create-issueIssue #762, with a brainstorm, a spec and a plan2026-11-10 13:17 UTCimplement-issue #762Pull request #779: 2 commits, +95 −402026-11-11 12:07 UTCmerge-pr #779CI green, squash-merged, issue closed2026-11-11 12:24 UTCTagout is built with Tagout. Read from this repository's tracker on 2026-11-11 by scripts/site-figures.py.
Three ways an agent-driven change goes wrong without anyone noticing, and the lock that stops each one.
Four agents share one checkout, and a commit lands in another agent's pull request.
Guarded git writes check the branch before and after, and the write-gate denies the raw command.
The fix ships before the cause is known.
debug-issue finds the root cause before any patch.
The backlog only ever fills.
One filing bar for every inlet, and triage-backlog to re-decide what is already open.
Once installed, say what you have. Each row is a skill or a command, and each one ends with a recap and the next command to type.
| Situation | Reach for |
|---|---|
| An idea to track | create-issue |
| An issue with a plan | implement-issue #N |
| A PR to land | merge-pr #N |
| One idea or issue to a merged PR, hands-off | deliver-issue <idea> or #N |
| A queue that never shrinks | triage-backlog |
| Many issues, hands-off | auto-dev |
| What went wrong in my last sessions | review-sessions |
| A legacy .NET app | The .NET add-on |
| A new repo for these skills | /tagout:init |
| Something is already broken | debug-issue fires on its own |
The add-on cleared three apps from dead platforms in 18 minutes (Chords), about 30 minutes (Les Fleurs du Mal) and about 1 hour (Pokédex G), timed from the gate commits. The apps, the seven phases and the install line are on the .NET add-on.
The method in full, the decisions behind it, and one article per release.