command-development

You design slash commands by defining YAML frontmatter fields such as description, agent, model, and subtask, then packaging them with actionable templates. This standardizes command structure and enables rapid deployment across projects and team workflows.

Yes, slash commands support dynamic arguments, file references, and bash execution patterns. These features allow you to build powerful, flexible command templates that can interact with different project files and accept runtime parameters.

The best way to structure slash command templates for team reuse is to apply consistent YAML frontmatter conventions and modular patterns. Standardizing fields like agent and subtask ensures commands are secure, clear, and easily reusable across different workflows.

No external dependencies are required to build slash commands for OpenCode. The command development process relies entirely on native OpenCode frontmatter conventions, ensuring templates remain lightweight and portable across any project environment.

YAML frontmatter agent routing works by specifying an agent field within the command template definition. This directs the OpenCode system to process the command's actionable template using the designated agent and model for targeted task execution.

You should avoid modular slash command templates if your task requires a one-off, highly specific action that does not benefit from standardization or reuse. For isolated actions, maintaining strict YAML frontmatter conventions may add unnecessary overhead.