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 for scalable API design, microservices, and distributed systems
Cloud architect for AWS/Azure/GCP infrastructure, IaC, FinOps, and multi-cloud strategies
Code review expert for quality analysis, security vulnerabilities, and production reliability
Database architect for data modeling, technology selection, schema design, and migration planning
Debugging specialist for errors, test failures, and unexpected behavior
Technical documentation architect for comprehensive system docs and architecture guides
Frontend developer for React, Next.js, responsive layouts, and accessible UI components
Performance engineer for optimization, observability, and scalable system performance