SDD reflection — same talk different world¶
March 16, 2026 · LinkedIn
11 reactions · 0 comments · 491 views
Tomorrow I'm presenting Skill-Driven-Development again. This time for Fremra and Clave.
When I first ran the presentation, I had a methodology. That turned out to be just the start.
Since then I've built four things I didn't anticipate needing:
Synthesis — because agents navigating large codebases were flying blind.
KCP — because there was no standard for what an agent should know before it acts.
kcp-commands — because 289 CLI tools were silent knowledge gaps.
kcp-memory — because agents also need temporal context, not just structure.
Now I'm watching the MCP ecosystem grow fast. Tools, orchestration, agent loops everywhere.
But most of what I see is focused on actions — what agents do. Very little on knowledge — what they know before they act. The structured context layer that tells an agent what exists, what the conventions are, what scope it's operating in.
A few people are starting to notice the gap. Public sector architects. Infrastructure teams. Developers tired of agents guessing.
That's the piece I keep coming back to.
Curious how others are thinking about this.