The context rot problem is where most vibe-coded projects start unraveling. You get clean results on the first twenty files, then the agent starts confidently r

The context rot problem is where most vibe-coded projects start unraveling. You get clean results on the first twenty files, then the agent starts confidently rewriting things it already handled correctly because it's lost the thread. I've watched non-technical builders burn weeks at this exact stage. Not because the idea was wrong, but because the model needed more scaffolding than they knew how to give it. Your insight about hook-enforced delegation versus polite suggestions via Claude.md is spot-on. The Claude.md file is documentation the agent treats as optional under pressure. What you built is closer to how a real multi-person team works: not "hope everyone read the doc," but hard-coded routing that actually fires. The fact that you arrived at this without a formal engineering background makes the story more interesting, not less. What's the actual product you were trying to ship when you realized you needed this? The plugin makes sense as a byproduct of something bigger.