agent-directory

To discover specialist agents for task delegation, scan your local agent directory and read the agent metadata frontmatter to determine capabilities. The system then invokes the best-matched specialist agent for the task by using the frontmatter 'name' value as the subagent_type.

Agent metadata frontmatter works for task routing by providing the capability details and the 'name' value required for invocation. The system reads this frontmatter from agents in your local directory to prioritize specialist domain expertise before falling back to generic categories.

The best way to automate code review or design validation is to delegate the tasks to specialist agents in your local library. The system scans the directory, reads the frontmatter, and invokes the agent with the matching domain expertise for the specific task.

Yes, you need agent metadata frontmatter to enable task routing. The system requires this frontmatter to determine agent capabilities and specifically uses the frontmatter 'name' value as the subagent_type for invoking the correct specialist for delegation.

When no specialist agent matches your task during delegation, the system applies a fallback mechanism. It defaults to invoking generic agent categories to handle the task when no specific domain expertise is available in your local agent directory.

Specialist agents for local task delegation are stored in your agent directory, specifically located at ~/.config/opencode/agent/. The system discovers available agents by scanning this folder and reading their metadata frontmatter to determine their capabilities.