The skills/ directory pattern is the same in our setup. We've got one markdown file per architectural decision the agent kept getting wrong, and they all get re-read at the start of every session. After a few sessions there's not much left to re-explain.
Scalability is harder to catch with a hook alone. We've started writing the quantified threshold into the spec ('handles 30k rows in under 2 seconds'), so the agent flags it itself before I'd otherwise need to interrupt.
Nice. The thing I'd point to in what you did is that the consensus ends up written in a doc the agents re-read, rather than only living in the session that produced it. That's the same reason the per-decision markdown files have stuck for me - the agreement survives the context window, so the next run picks it up instead of going over it again. I'll read through the synthesis proposal. Multi-agent coordination is one I haven't spent much time on yet.
Adam Lewis
Product Engineer/Architect navigating the AI revolution
The skills/ directory pattern is the same in our setup. We've got one markdown file per architectural decision the agent kept getting wrong, and they all get re-read at the start of every session. After a few sessions there's not much left to re-explain.
Scalability is harder to catch with a hook alone. We've started writing the quantified threshold into the spec ('handles 30k rows in under 2 seconds'), so the agent flags it itself before I'd otherwise need to interrupt.