What problem does it solve?
This skill provides expert guidance for creating Opencode slash commands, helping teams design, structure, and standardize prompts that trigger reusable workflows within Opencode.
Core Features & Use Cases
- Frontmatter-driven command design: ensures each command has a mandatory name and description, with optional argument hints and tool restrictions.
- XML-structured body enforcement: requires sections like <objective>, <process> (or <steps>), and <success_criteria>, plus optional <context>, <verification>, <testing>, and <output> tags.
- Project and personal command scope: covers both project-local (.config/opencode/commands/) and user-wide (~/.config/opencode/commands/) directories.
- File naming and invocation: clarifies how command-name.md maps to /command-name and how to reference files or contexts.
- Generation protocol and best practices: provides a repeatable template approach to create high-quality, safe, and scalable commands.
Quick Start
Create a new command file named <command-name>.md under .config/opencode/commands/ and populate it with YAML frontmatter (name and description) and an XML-structured body.
<quick_start_instruction>Use this process to introduce a new slash command: write the file, ensure frontmatter correctness, and implement the XML body with objective, process, and success criteria.</quick_start_instruction>