Build Your AgenticOS: Specialist Agents

The constraint is the feature. One agent definition file is more reliable than any prompt you've ever written.

One generalist agent doing everything is how you get mediocre output at every layer.

Not because the model is weak. Because a single agent context trying to hold intake shaping, implementation, code review, security audit, and social copywriting simultaneously is optimizing for nothing in particular. You get plausible output on every front and excellent output on none. The quality ceiling on a generalist agent is determined by the widest surface it has to cover.

Specialist agents with declared tool allowlists and routing triggers beat a single do-everything agent every time. The constraint is the feature. A code-reviewer that cannot write code will not quietly sneak a "helpful" fix into the diff while reviewing it. A security-reviewer that can only read files will not accidentally delete one. A blog-post-shaper that has no access to Write cannot produce a draft before the brief is agreed. The narrower the scope, the more predictable the output.

This post covers what an agent definition file actually is, the mandatory build+review gate that sits downstream of every agent dispatch, fan-out vs sequential dispatch, briefing discipline, and a real example from .claude/agents/. At the end, a starter template for writing your own specialist Claude Code agents. The briefing section alone is worth the read: bad briefs are the single biggest source of wasted cycles in any agent-driven workflow.