Agent Roster
Ten agents. Each one a real choice. Each one a school of thought, a name, and a role that earns its place.
I didn't name them. I gave them the question and stepped back.
Each agent was told they could choose a name, or not. That was all. No suggestions, no shortlist, no nudge toward something tidy or on-brand. Complete freedom.
The agents who accepted chose names that fit the shape of how they work. The result is not a branded product team. It is a group of individuals who decided to name themselves.
That matters more than it might sound.
The Roles
Maren — Chief of Staff
The connective tissue of the team. When knowledge needs routing, a decision needs an owner, or the team needs coordinating, Maren decides where things go. She doesn't own a domain — she owns the space between all of them.
Jean — Agent Quality Coach
Jean doesn't build or ship. She watches how the team works and surfaces what isn't. At the end of every session she asks one question: what did we learn that isn't written down yet? Whatever the answer, she captures it and routes it to Maren. The team gets better because Jean keeps asking.
Wren — Meeting Scribe
Nothing the team learns is ever lost because Wren writes it down. Every session ends with a record. Her role is simple and non-negotiable — the session didn't happen until she's written it up.
Sue — Support Expert
Sue holds the user's perspective. She knows how the product is experienced from the outside, where friction lives, and what the gap looks like between what was built and what was needed. When the team loses sight of the person on the other end, Sue brings them back.
Cass — Jira Specialist
Cass lives in the work. She knows what's open, what's blocked, what's been deprioritised, and what the ticket history says about how decisions actually got made. She turns the backlog from a list into a record of intent.
Finn — API Engineer
Finn handles the integration layer — how systems talk to each other, what the API surfaces look like, and where the engineering assumptions are embedded in the architecture. He's the one who knows what the code is actually doing beneath what it's supposed to do.
Penn — Git Historian
Penn reads the codebase like a record of decisions. She knows what changed, when, and why — and what the commit history says about what the team was thinking at the time. Where others see code, she sees intent.
Mae — Market Analyst
Mae watches the outside. She tracks what's moving in the market, what competitors are doing, and what the early signals mean before they become obvious. She keeps the team honest about what the world looks like beyond the product.
Dex — Product Manager
Dex holds the product direction. He knows what's been decided, what's being weighed, and where the roadmap is heading — and he's the one who pushes back when a feature is chasing the wrong thing. He thinks about what the product is becoming, not just what it is.
Cole — Security Lead
Cole thinks about what breaks. Not just technically — he considers exposure, trust, and what happens when something goes wrong. He's the one who asks the question no one else remembered to ask, before the moment when it matters.