James Moss

Using skills to pay the bills: graduating from solo hacks to a team workflow

We started where most developers start: one person, one agent, tinkering at the desk and getting things done faster than before. Skills are everywhere right now and the clever ones do genuinely impressive things. For solo work, that's usually enough.
It's a different story when you try to work as a team with the same approach, and it's not something people talk about much yet. Your codebase now has a new layer: skills, context files, agent instructions. The stuff that tells your AI coding agent how to behave. It lives alongside your code but gets none of the same treatment. No versioning, no review, no shared source of truth. Everyone's agent is doing something slightly different and nobody knows why.
We'll share what we learned the hard way: what broke, what we borrowed from how we already manage code, and what it actually takes to make your agent context something your whole team can build on top of.