subagent-authoring

To create a valid OpenCode subagent definition, place a Markdown file in the .opencode/agents directory and populate the required frontmatter fields including name, description, mode, model, variant, prompt, and hidden to enforce the caller protocol.

Required frontmatter fields for an OpenCode subagent are name, description, mode, model, variant, prompt, and hidden. Defining these fields enforces the required caller protocol and return contract for valid subagent execution.

Safely refactor an existing OpenCode subagent by applying a structured workflow to update Markdown files in the .opencode/agents directory, validating that frontmatter conventions and the return contract remain intact to prevent configuration drift.

OpenCode subagent configuration fails when Markdown files lack clear conventions or required frontmatter fields like name, description, mode, model, variant, prompt, and hidden, leading to misconfigurations and drift during authoring or refactoring.

Yes, you can store OpenCode subagent definitions in a global agent directory outside the local .opencode/agents path. The required frontmatter fields, caller protocol, and return contract apply equally to both global and local subagent Markdown files.