I started with the same approach. But not go the opposite route.
The problem is too many one of skill eating up context.
I now create routing skills. Each skill take cares of one domain.
And I compose using references, with cyber-agentkit
Skills can call other skills. They're basically composable functions written in English.
So, like a function, I prefer naming skills with a leading verb:
/open-pr
/audit-instructions
/review-pr-comments
Context about to compact? Run /checkpoint create first.
It saves where your agent session stands: next step first, settled decisions, dead ends. /checkpoint resume continues it in a fresh session in any harness and repo.
repobuddy 4.0 (was /session):
repobuddy.github.io/repobuddy/skil…
Great to learn a new word (for me) epistemological from @ploeh
If I can pronounce it correctly. 🤣
In my own words, it's discovery of intent.
Which leads to Spec Driven Development.
I think that in your post on verification-first development you buried the real benefit of TDD, or perhaps didn't notice it, although you did include it.
In my view, the most important benefit of TDD is epistemological. blog.ploeh.dk/2025/10/20/epi…
