subagent-best-practices

To define a Claude Code SubAgent, use YAML frontmatter in `agents/*.md` files by specifying mandatory fields like `name`, `description`, and `tools`, alongside recommended fields such as `model` to ensure proper agent configuration.

The mandatory 3-Phase structure for Claude SubAgent definitions consists of initialization, feedback handling, and finalization phases, ensuring agents function as intended and communicate effectively throughout their lifecycle.

Claude SubAgent tool access and context passing failures often stem from incorrect tool selection in YAML frontmatter or missing context passing mechanisms, which can be diagnosed by reviewing anti-patterns in the agent definition.

Best practices for Claude SubAgent context passing involve implementing effective context passing mechanisms within the agent definition to ensure the SubAgent receives all necessary information for its specific role.

Choosing the right tools for Claude SubAgent roles requires using optimal tool selection strategies within the YAML frontmatter, matching the specified tools array to the specific tasks the agent needs to perform.

Common anti-patterns to avoid when defining Claude SubAgents include incorrect tool usage, missing context, and communication failures, which prevent the agent from functioning as intended.