Broad agents, niche skills.

This is the architecture rule I keep coming back to: build a few broad, capable agents that each own a whole domain, and give them a library of sharp Skills they pull from as needed. Don't build forty tiny specialist agents all pretending to be departments.

It feels backwards at first. You'd think more specialized agents means more precision. But over-specializing the agents usually makes the whole system more fragile. One broad agent that knows your business and can reach for the right skill beats six narrow ones that each only do one thing.

The skills are where the specialization lives. The agent stays broad and capable, and the skill is the niche expertise it loads the moment it needs it. That split keeps the whole thing simple enough to maintain.