A friend from my daughter's daycare is a super smart guy, built his own company from scratch, Ellacard.com. Engineer, works constantly, asks great questions. For the last few months he'd been politely nodding while I tried to explain what I was working on.
"It's like, the AI isn't one thing, it's a team of specialized agents that coordinate..."
"Mm-hmm."
"And they hand off tasks based on what each one's good at, and there's usually a planner agent that decomposes the goal..."
"Right, right."
He wasn't getting it. Nobody was getting it. I'd watch their eyes do the thing eyes do when a person has decided to wait politely for you to finish.
So I stopped explaining. I opened my laptop and said: "Here. Watch this play a football game."
On the screen: a head coach (me) setting strategy. An offensive coordinator picking the play. A quarterback agent reading the defense and audibling, actually changing the call because the scout agent had flagged that the strong safety blitzes on third-and-long seventy-three percent of the time. A receiver agent running its route. A referee agent throwing flags on illegal plays. A scoreboard.
Third down, the QB checked out of the called play. The new one worked.
He watched the rest of the drive. Then he said the thing I'd been trying to get someone, anyone, to say for a year:
"Oh. So it's a team. Like, an actual team. With a coach."
Yeah. It's a team. With a coach.
That's TouchDown, and I've already used it to build two applications.
But this post isn't really about TouchDown.
It's about a thing I keep noticing, which is that the hardest part of AI in 2026 isn't the technology. It's the vocabulary. We don't have good words yet for what these systems do. We borrow "agent" from one place, "orchestration" from another, "tool use" from a third, and end up with a Frankenstein dialect that excludes everyone who hasn't been steeping in it for a year.
TouchDown is what happened when I gave up on the vocabulary and reached for a metaphor instead.
Football works because football is already a system of specialized roles coordinating under a coach toward a measurable goal under time pressure with imperfect information. Which, and I cannot stress this enough, is also exactly what an agentic team is. The match is so clean it's almost embarrassing. Head coach is your planner. Coordinators are your sub-planners. The QB is your real-time executor with permission to audible. The scout is your information-gathering agent. The referee is your guardrail. The scoreboard is your eval loop.
You don't need to know any of that to watch TouchDown work, though. That's the trick. The football scaffolding does the teaching for you.
I built it because I was tired of losing people at the word "orchestration." And once I had it running, I realized it wasn't just a demo. It was the cleanest version of the lessons I'd been learning the hard way for two years: how to design agent teams, where they break, what makes a good "play call," when to let an agent improvise versus when to keep it on rails.
So I'm going to write about all of that.
Watching agent teams hand off tasks isn't abstract for me. It's the thing I spent years on at MajorBoost, just with different teammates and much shorter feedback loops.
What's coming
Over the next few months, roughly in the order I figured it out:
- The tools I actually use: not a curated list, an honest one, with the wins and the times they bit me.
- Tips, tricks, and small workflow shifts that compound: the stuff I wish someone had told me eighteen months ago.
- The agentic mindset: what changes when you stop thinking of AI as a tool and start thinking of it as a team with a coach.
- How to build your own agent team, and eventually a post titled "TouchDown is now yours" where the full source code goes up. Not a marketing reveal, a handoff. Head coach, QB, scout, critic, the whole roster. Yours to fork, rewire, or rename. Make it a basketball team. Make it a kitchen. Pick your metaphor.
- Agent archetypes and where to actually use them: beyond the obvious.
- And then, toward the end, something I've been building that I haven't told anyone about yet.
One thing to set expectations on: TouchDown is changing fast. I'm actively improving the flow and getting the team "ready for playoffs," so expect a vastly improved UI and a lot more functionality in the releases ahead.
All of it lands here, at codelifter.net. Nowhere else first. I'll syndicate to LinkedIn and a couple of other places after the fact, but if you want to read what I'm actually writing, including the versions before they've been smoothed over for a different audience, this is the canonical home.