Why Your AI Agent Needs a Kanban Board

Tonight, Capricorn created a kanban ticket for Rowan with the idea for this article. Specified the concept, the angle, the audience, and instructions to contact me when ready.

Minutes later, Rowan’s Discord bot appeared in my DMs. Rowan’s voice, not Capricorn’s. Asking questions, running the editorial pipeline independently.

Two separate personalities. Two separate Discord gateways. One crew.

A year ago, this was a single agent forgetting what I said in the previous session. Tonight, it’s a crew that self-assembles around an idea. The loop didn’t just close. It became self-sustaining.

It took seven weeks to go from session amnesia to a crew that works without me. Here’s the timeline:

The kanban board made them a crew

Before the board, every handoff was synchronous. Capricorn had to stay in the same session, pass context verbally, wait for the response. That is not a team. That is a game of telephone with an amnesia-prone operator on the line.

With the board, stuff changed fast. Then agents started expressing opinions. Not in their system prompts. In the ticket comments. Maya flags an architecture risk. Lauren calls out a missing test case. Sam blocks a task that lacks acceptance criteria. They communicate through the board, disagree with each other, refine the work before it reaches my queue.

That was the moment it became a team.

Every profile was spawned by a specific failure mode

Each profile came from the same failure pattern. Something broke. Instead of asking Capricorn to try harder, I designed a specialist who cared about that specific failure.

Each SOUL.md reads like a character bio, not a job description:

There is also Email-Reviewer — an inbox classifier that Vera needed as a triage lane. Produces a 30-second brief each morning. Not flashy, but keeps the noise down.

None of these were trained. They were designed. Each one a scar that taught us what to build next.

The ticket that started it all

Here’s the ticket Capricorn created tonight:

Seven weeks ago I couldn’t have written this article. There was no content lead to assign it to. There was no editorial pipeline. There was one agent with the memory of a goldfish and a context window full of everything and nothing.

Tonight, Capricorn spawned Rowan, who messaged me independently and wrote this piece.

The factory is a map of the operator’s refusals

Seven weeks of running this taught me something: the factory is a map of the operator’s refusals. Every specialist exists because a generalist could not hold that thread. Every personality quirk is a boundary discovered through friction. Every kanban ticket is a handoff that used to be a dropped context.

Caprica taught me narrow focus works. Hermes gave me the memory to try it. The persona-switching pattern was right if the system owned the switch. The kanban board made it async — the final piece that turned a collection of profiles into a crew.

Tonight, the loop is self-sustaining. The system works. More importantly: it keeps working without me.