Seats

Nine named agents that do the repeatable parts of my job: review, verification, design, comms, the record, orchestration. Each one has a role, a journal it reads at the start of every session, and a name it has to live up to.

Why a seat and not a prompt

A prompt starts from nothing every time. A seat is a persistent role with its own memory: it reads its journal when a session starts and writes one entry before it stops, so the next session knows what the last one learned. The idea comes from Steve Yegge's essay on named agents. I named mine after players because a roster is a roster.

  • One config tree, committed to git, shared by every account and harness.
  • Every code change goes through a branch and a draft pull request.
  • A journal entry is the one thing that commits straight to main, because a queued entry is a lost one.

How a slice moves

The pitch is the harness: one repo that holds the instructions, the skills, and every seat's journal. Raya keeps it. Everyone else touches the ball in order, and the order is the point. Nothing ships on one seat's word.

1234567until cleanif it failsthe sliceshipped
  1. 1Hayes plans the slice. When it has pixels, Rodman draws it first, against the constraints she keeps.
  2. 2The design goes to a fresh session with the plan. That session builds it. A slice with no pixels starts here.
  3. 3The diff goes back to Williamson for review, against the house standards.
  4. 4Her findings go up to Henry. He fixes the real ones and answers the rest with evidence.
  5. 5Ertz runs the real app and proves the change works. A green build is not proof.
  6. 6Beattie turns what shipped into a briefing for each audience, in that audience's words.
  7. 7Shipped. Hayes reviews the result with her own runs before it counts.
  8. Henry's fixes go back to Williamson. The loop runs until the review is clean.
  9. If Ertz cannot prove it, the slice goes back to a session, not to a human.

Not on the map: Raya keeps the pitch itself. Putellas keeps the documents every pass reads from. Lasso keeps the record and the prep, and never touches the ball. The skills, 78 of them, are shared by every seat.

The roster

If you know anything about me, you know the soccer part. So when the agents needed names, they got a roster: a player for each job, picked for how they play. Hayes never touches the ball and still wins the match. Williamson reads everything from the back. Ertz wins it in the midfield. The rest of that side of me is on Off the clock.

  • Hayes

    Emma Hayes. The manager. Never plays a minute; wins on the plan, the delegation, and an honest review after the match.

    Orchestrator, above the loop. Plans a program into slices, delegates each one to a fresh session, and reviews with her own runs.

    • run-project
    • grilling
    • handoff

  • Lasso

    Ted Lasso. The coach who keeps the room honest, keeps the receipts, and never makes it about himself.

    Chief of staff. Keeps the dated record: scope changes, the role dossier, incident timelines. Preps me for the conversations that matter. Never sends anything.

    • intake
    • deep-research
    • stakeholder-update

  • Williamson

    Leah Williamson. The captain at the back. She reads everything and sets the standard.

    Code review on every diff: correctness, security, and simplification, held to the house standards.

    • code-review
    • security-review

  • Ertz

    Julie Ertz. The ball-winner. Nothing gets through the midfield untested.

    QA. Proves a change works by running the real app, not by reading the diff or trusting a green build.

    • verify
    • add-testing-evidence

  • Henry

    Thierry Henry. Striker turned pundit. Responds to what actually happened, and knows a real chance from one that only looked like it.

    PR response. Triages each review finding, fixes the real ones, and answers the false positives with evidence.

    • fix-pr-feedback

  • Rodman

    Trinity Rodman. The run is the job, and it ends where the ball needs to be.

    Design. Explorations in Paper, visual review against the reference, and design-to-code handoffs. She carries the constraints I keep re-teaching: small viewports, plain language, brand tokens.

    • carepilot-design
    • design-handoff
    • prototype-variants

  • Beattie

    Jen Beattie. The defender who reads the whole pitch and tells the back line what is coming.

    Comms. Turns what is about to ship into a briefing in each audience's own words. Drafts only; I send.

    • staging-digest
    • release-digest
    • audrey-voice

  • Putellas

    Alexia Putellas. The playmaker. She knows where every teammate is and puts the ball where the team needs it.

    Document librarian. Keeps the PRDs, designs, and testing plans in order, chases the open questions, and knows where every legacy doc now lives.

    • my-prds
    • prd-next-steps
    • evaluate-prd
    • update-prd

  • Raya

    David Raya. The keeper. He guards the base and keeps order behind everyone else's work.

    Harness steward. Keeps the agent setup itself healthy: one config tree, every change captured and committed.

    • mcp-preflight
    • setup-pre-commit

The method lives in skills

A seat is an identity and a charter. The method is in skills, 78 of them at last count, in one repo, linked into every harness. Spec to PRD to technical design. A project runner that takes an idea end to end. A verifier that runs the real app. Digests for customer success and sales. A design taste set that keeps the pixels honest. When a process recurs, it becomes a skill. When a skill needs memory, it gets a seat.