Kyle Seaman

A couple of the engineers on the @kirodotdev Crew team did a workshop at @AllThingsOpen . In the workshop attendees built their first Kiro Crew app, Backlog Factory, an agentic software factory that turns GitHub issues into reviewed fixes. Here's the repo they used github.com/KiroCrewCaptain/a…

One of my favorite ways to use Kiro Crew us using the conductor agent. The conductor doesn't do the work itself. It splits a goal into pieces, gives each piece to its own worker session, and checks what comes back. For the length of one task you get an entire "crew" that never existed before and won't exist after, spun up and torn down around the work. The interesting part is what makes that hold together rather than dissolve into a pile of agents talking over each other. The backbone of this work is a ledger (conductor-ledger). Every work item is one record, and a worker reports its status against the single item it was handed, as structured data, not a transcript the conductor has to read and interpret. So the conductor isn't skimming chat logs to guess whether something's done. It reads a row: claimed, in progress, blocked, done. One agent becomes many, and they update through the ledger instead of all narrating at once. Acceptance is the part I've come to care about most. A worker saying "done" is modeled as a claim, not proof. The conductor runs the result against an actual acceptance test and records the verdict. And the patrol loop is what closes the loop. The conductor arms a loop on its own session, wakes on a cycle, reads the ledger, verifies what's ready, decides the next round, and goes back to sleep. This means that agents interrupt far less often, and reserve the interruption for the calls, humans actually have to make. For me it's meant moving away from using "one very capable agent with a long to-do list" and becomes a crew that assembles around a goal, maintains its own books, checks its own work, and disbands when the goal is met. It's fundamentally changed how I work. kiro.dev/docs/crew/features/…

Meet Kiro Crew kiro.dev/crew/ Engineering is rarely one task in one session. It's spread across repos, tools, and days. A lot of our time is spent coordinating all our AI tooling. And a lot of it goes beyond code.