command-writing

<!-- cloud_safe: degrade --> # command-writing ## When to use * Creating a new slash command in `src/agent-src/commands/{name}.md` * Rewriting an existing command (not a typo fix) * Deciding whether a request should be a command at all * Splitting an oversized command into smaller ones Do NOT use this skill when: * The content is a constraint the agent must always honor → use `rule-writing` * The content is reference knowledge agents cite → use `guideline-writing` * The content is a triggered workflow invoked by the model → use `skill-writing` ## Command vs skill — critical test | Intent | Artifact | |---|---| | "User types `/foo` to explicitly run this" | **Command** | | "Agent picks this up from description match" | **Skill** | A command is **user-invoked** and carries `disable-model-invocation: true`. A skill is model-invoked via description routing. If both audiences apply, author as a skill and add a thin command that delegates to it. **A command must EARN a top-level slot.** Only three justifications qualify: **flow-entry**, **state-query**, or **product-surface** — everything else is a skill. Check before authoring: [`command-clusters` § Command justification](../../../docs/contracts/command-clusters.md#command-justification--a-command-must-earn-a-top-level-slot) ([ADR-048](../../../docs/decisions/ADR-048-command-justification-rule.md)). **Categorize at creation (checklist).** When you author a NEW top-level command, declare its justification as a `category:`...