What I do

Engineers lead agents

One or two engineers directing a staff of agents, with a product lead, own a milestone end to end. Spec and tests come before code, and only live counts as done.

The problem

Most engineering organizations got AI and kept everything around it: the stories and the sprints, the daily stand-ups, the line-by-line reviews, the sign-offs, the hand-offs from specialist to specialist, and done meaning merged. We are still building software with the methodologies of the year 2000, and writing code is no longer the slowest part of the work.

How I approach it

The unit I build with is one or two engineers who direct a staff of agents, and a product lead who focuses on the customer’s experience. Work is assigned as a milestone, not as features or stories, and the engineers own everything after the goal is set.

  • Two engineers when coverage matters. A milestone that cannot stop when one person is out gets a second engineer.
  • Start with work the code can explain. The first milestones are bug fixes, security fixes, technical debt and self-contained features: work where everything the engineers and the agents need to know is already in the code, with no outside decisions to wait for. As each one lands, the engineers take on larger pieces.
  • Spec and tests before code. The goal becomes a testable spec, the scaffold and the tests are built before the implementation, and the agents build inside those guardrails.
  • A fix proves itself. A fix is not accepted until a test fails without it and passes with it. Whoever wrote the code does not test it, person or model.
  • Review by risk. A person reviews closely the changes that can do the most damage (shared services, authentication, payments, personal data) and the hotspots, the parts of the code that break most often. At this volume nobody can review every line, so the gates and the tests catch the rest.
  • Every engineer runs agents, manages the results, and is accountable for it all.
  • Status in writing, decisions live. Progress is reported in writing, so nobody holds a meeting to hear a status update. Meetings are kept for decisions: approving the brief and the plan in one conversation, and a weekly demo of working software, which takes the place of sign-offs. A meeting that decides nothing is dropped.
  • Done means live. Done means built, tested, released, monitored and seen working in production.
  • Plan with a vision and milestones. The plan starts from a vision: where the users should be in six months or a year, and what they will be able to do. The milestones are the steps expected on the way there, a forecast rather than a promise, and they take the place of a list of features and stories. No date is given without a written, testable definition of done.

What it produces

A delivery method written down for the organization’s own teams, and the first team running it.

In the Luci House

The AI-staffed team I run every day as a working prototype.

The members built the platform they run on, and the tools they use: 6,477 commits since June 1, 2026 and 27 tools, with more than 25,000 tests run before every release. Whoever wrote the code does not test it: the quality engineer tries to break a change before it is accepted, and a fix is not accepted until there is a test that fails without it and passes with it. Work is implemented, then verified, then live, and only live counts as done. What it has built, and the release gates

Figures as of November 20, 2026.

All of What I do