[dmppch]

The role decomposition — distinct specialist personas for planning, review, QA, shipping — is the pattern worth paying attention to here, separate from the LOC debate. Then making them work together in a panel/team format.

I've been working on agent workflow tooling and what keeps surprising me is how quickly authoring the skills becomes the trivial part compared to keeping them composable and in sync across projects.

gstack's git-clone-and-copy install model works great solo, but I'm curious how it holds up when different repos need divergent review gates or QA flows — that's where every "just copy the skills folder" approach I've seen starts to buckle.