Before the shitstorm rolls in: of course loops aren't for noobs. It's a burner headline. :) There are some genuinely great loop concepts out there.
But here's my problem with most of them: they're completely one-dimensional. Why?
When /loops started trending I'd already been living in Claude Code for three weeks. So on June 19 I actually said it out loud to a colleague: loops-are-for-noobs. How can I say that with a straight face? Because I'd been running /teams successfully for a good week by then — and next to that, /loops and /skills just felt lame.
/teams is just the logical next step
The thing is, /teams isn't a competitor to any of that. It's a combination of all of it:
- skills
- loops
- routines
- guardrails
- hooks
- agents (and team-agents)
- training (or briefing)
- visualisation (my dashboard)
- ...
But multi-dimensional. The list doesn't end there — you add whatever you can imagine to it.
Loops vs. teams, with rockets
We live in scary, crazy times, so let me use rockets as the example.
Loops are the old-school kind: lock the target, go for it no matter what. Teams are the smart kind: they read the situation and react.
And that's the whole point, because development — for me — has never meant "reach a certain target no matter what". It's always meant: solve the client's problem, in the best (or easiest) possible way. Or just make the thing possible at all.
A loop can't do that. A team can.
That's exactly why my vision of the company of the future isn't a bigger loop. It's something else entirely — beyond your imagination:
