Ship in parallel
Many agents. Clear ownership.
Agentic Dev Model
Ship more agent work without losing control.
You name an outcome. The Mailman seals it into a package. The Mayor delivers it — safely, in parallel, with proof attached.
- Name an outcome, not a hundred tickets.
- Work gets sealed into one package.
- Many agents build it at once.
- Humans stay on every real decision.
What This Allows
More output. Less guessing.
Agents move fast because the shape is fixed.
Trust the queue
Every issue has a state.
Review faster
Proof is already attached.
Improve the system
Bad runs create better skills.
The Mailroom
Three roles run the shop.
Open. Seal. Deliver. In that order, every time.
01 · open
Workbench
Are you clear to work? The Workbench runs a health check — repo, tools, Linear — and points you at where to start. Nothing happens until the light is green.
02 · seal
Mailman
You name an outcome — "move Plaid toward prod," "clear anything ready to ship." The Mailman reads the board, gathers the confirmed issues, and seals them into one package addressed to you. One decision: seal, or seal and go.
03 · deliver
Mayor
The Mayor checks your mailbox, opens your package, and delivers it — running each piece of work by its state, watching every PR, holding the caps. It surfaces green work to merge and yellow calls for you.
Packages
What's in the box.
A package is a claim on real work — not a file.
Addressed to you
Every package is stamped packaged:you. Only your Mayor opens it — no one else's touches your work.
Confirmed only
Nothing half-baked gets sealed. Work is verified before it ever goes in the box.
One claim, no collisions
A sealed package is your work-in-progress. Two operators can run at once and never step on each other.
Lives in Linear
The package is a label on real issues, so the board is always the single source of truth.
Flow
One path from outcome to merge.
Everything leaves state behind.
Outcomewhat you want
Confirmverify scope
Packagesealed work
Claimone owner
Buildworktree
Evidencetests + notes
Reviewchallenge
PRready change
Polishvisual lane
Mergehuman gate
Skills
The skills behind the roles.
Each skill owns one boundary.
workbench
Green-light health check, then point at where to start.
plan-feature
Break big ideas into projects and issues.
new-issue
Capture one piece of work.
confirm-issue
Verify scope and write the fix plan before build.
forensic-issue
Trace data gaps read-only, on live data.
mailman
Seal an outcome into a sealed package.
work-issue
Ship one confirmed issue, proof attached.
work-batch
Clear many confirmed fixes at once.
polish-ui
Finish visuals after behavior is real.
session-retro
Turn run failures into better skills.
mayor
And the Mayor — the control plane over all of them.
Not a skill you call. It's the one that calls them, watches the PRs, and holds the caps.
Built On
Runs on tools you already trust.
The board, the models, the muscle.
Linear
Claude
Codex
Human Gate
Show green work and yellow decisions.
Humans should not hunt for risk.
Green
Proof passed. Review is clear. A human can merge.
Yellow
Scope, proof, or product judgment needs a human.
cap
When decisions pile up, agents stop.
Clear the queue before creating more work.