octo
The `/octo:octo` command is a legacy redirect that forwards user queries to `/octo:auto`, the smart routing system for the Claude Octopus workflow. Use this command when you encounter older references to `/octo:octo`, though `/octo:auto` is now the recommended entry point for intelligent provider routing and multi-agent orchestration.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/nyldn/claude-octopus/HEAD/.claude/commands/octo.md -o ~/.claude/commands/octo.mdocto.md
# /octo:octo → /octo:auto (Legacy Redirect)
This command has been renamed to `/octo:auto`. Invoking `/octo:octo` still works for backward compatibility.
## EXECUTION CONTRACT (Mandatory)
When the user invokes `/octo:octo <query>`, you MUST:
1. Inform the user: "Note: `/octo:octo` has been renamed to `/octo:auto`. Routing your request now."
2. Immediately invoke: `Skill(skill: "octo:auto", args: "<full user query>")`
3. If the routed workflow dispatches multiple providers, surface `${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh agent-summary` before final synthesis when available.
Do NOT duplicate the routing logic here — delegate entirely to `/octo:auto`.Backend architect. Delegate only when the user explicitly starts an Octopus workflow.
Cloud architect. Delegate only when the user explicitly starts an Octopus workflow.
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
Database architect. Delegate only when the user explicitly starts an Octopus workflow.
Debugger. Delegate only when the user explicitly starts an Octopus workflow.
Documentation architect. Delegate only when the user explicitly starts an Octopus workflow.
Frontend developer. Delegate only when the user explicitly starts an Octopus workflow.
Performance engineer. Delegate only when the user explicitly starts an Octopus workflow.