sk-create-command

Create Command

create-command is the command-authoring workflow packet of the sk-doc parent hub. It creates and improves OpenCode slash commands under .opencode/commands/ with executable workflows, precise frontmatter, required input gates, least-privilege tools, and router/presentation separation when needed.

This SKILL.md contains the core creation workflow. Use the references/ route map (references/README.md), assets/command-template.md, assets/command-router-template.md, assets/command-presentation-template.md, and ../shared/ only for exhaustive examples, edge cases, and validator implementation detail.

This packet is lean and self-contained. The advisor identity lives at the sk-doc hub root; do not add packet-local graph-metadata.json.

1. WHEN TO USE

Activation Triggers

Use this packet when the request involves:

• Creating a new OpenCode slash command.
• Refactoring a command into a thin router plus owned presentation asset.
• Adding or fixing command frontmatter, especially argument-hint and allowed-tools.
• Designing command argument handling with $ARGUMENTS.
• Authoring a namespace command such as /namespace:action.
• Separating visible prompts, dashboards, result templates, or next-step wording into a presentation contract.
• Checking whether a workflow should be a command instead of a skill, agent, or one-off task.

Keyword triggers: create command, /create:command, slash command, OpenCode command, argument-hint, allowed-tools, command template, router presentation split, thin router, presentation contract, paired /create, $ARGUMENTS.

When NOT to Use

Use another sk-doc packet when:

• The request is to create a skill or parent hub. Use create-skill.
• The request is to create an agent. Use create-agent.
• The task is a README, install guide, feature catalog, manual testing playbook, benchmark package, flowchart, or changelog. Use create-readme, create-feature-catalog, create-manual-testing-playbook, create-benchmark, create-flowchart, or create-changelog.
• The task audits, validates, scores, or optimizes an existing command document. Use create-quality-control.
• The task is one-time work that does not need a reusable slash command.
• The command already exists and the user only wants runtime debugging.
• The requested workflow is destructive or externally privileged but lacks confirmation and rollback requirements.