From octo
Orchestrates multi-provider AI implementation with quality gates, dispatching work to external LLM providers via orchestrate.sh.
How this command is triggered — by the user, by Claude, or both
Slash command
/octo:developcommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Develop - Development Phase 🛠️ ## 🤖 INSTRUCTIONS FOR CLAUDE ### MANDATORY COMPLIANCE — DO NOT SKIP **When the user explicitly invokes `/octo:develop`, you MUST execute the structured workflow below.** You are PROHIBITED from doing the task directly, skipping the development phase with quality gates, or deciding the task is "too simple" for this workflow. The user chose this command deliberately — respect that choice. ### EXECUTION MECHANISM — NON-NEGOTIABLE **You MUST execute this command via the Bash tool calling `orchestrate.sh develop`. You are PROHIBITED from:** - Using `Skill(...
When the user explicitly invokes /octo:develop, you MUST execute the structured workflow below. You are PROHIBITED from doing the task directly, skipping the development phase with quality gates, or deciding the task is "too simple" for this workflow. The user chose this command deliberately — respect that choice.
You MUST execute this command via the Bash tool calling orchestrate.sh develop. You are PROHIBITED from:
Skill(skill: "octo:develop") because it resolves back to this file and loopsSkill(skill: "flow-develop", ...) because that internal name is not resolvable by the Skill toolorchestrate.sh calls because "I can do this faster directly"Multi-LLM orchestration is the purpose of this command. If you execute using only Claude, you've violated the command's contract.
When the user invokes this command (e.g., /octo:develop <arguments>):
Preflight — Ensure plugin root is resolvable (run via Bash tool FIRST):
OCTO_ROOT="${HOME}/.claude-octopus/plugin"
if [[ ! -x "$OCTO_ROOT/scripts/orchestrate.sh" ]]; then
helper="$OCTO_ROOT/scripts/helpers/ensure-plugin-root.sh"
if [[ ! -x "$helper" ]]; then
helper="$(find "${HOME}/.claude/plugins/cache" "${HOME}/Library/Application Support/Claude" "${LOCALAPPDATA:-/dev/null}/Claude" "${XDG_DATA_HOME:-${HOME}/.local/share}/Claude" -maxdepth 8 -path "*/nyldn-plugins/octo/*/scripts/helpers/ensure-plugin-root.sh" -print -quit 2>/dev/null)"
fi
[[ -x "$helper" ]] && bash "$helper" >/dev/null 2>&1 || true
fi
test -x "$OCTO_ROOT/scripts/orchestrate.sh" && echo "plugin-root:ok" || echo "plugin-root:missing"
If the output is plugin-root:missing, stop and ask the user to run /octo:setup.
Step 1 — Run provider preflight via Bash tool:
bash "${HOME}/.claude-octopus/plugin/scripts/helpers/check-providers.sh"
Use the actual preflight output to display the workflow indicator before dispatch:
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider implementation mode
List available providers and mark missing providers as (unavailable - skipping). If OCTOPUS_COMPACT_BANNERS=true, use this compact single-line format:
🐙 develop — Multi-provider implementation mode | codex ✓ | gemini (unavailable - skipping)
If no external provider is available, stop and tell the user to run /octo:setup; do not fall back to Claude-native implementation.
Step 2 — Run orchestrate.sh via Bash tool:
bash "${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh" develop "<user's arguments here>"
✗ INCORRECT:
Skill(skill: "octo:develop", ...) ❌ Resolves to this command file — infinite loop
Skill(skill: "flow-develop", ...) ❌ Internal name, not resolvable by Skill tool
Task(subagent_type: "octo:develop", ...) ❌ This is a skill, not an agent type
CRITICAL: After the workflow completes, you MUST ask the user what to do next. Do NOT end the session silently.
AskUserQuestion({
questions: [
{
question: "Development phase complete. What would you like to do next?",
header: "Next Steps",
multiSelect: false,
options: [
{label: "Move to Deliver phase", description: "Validate and review the implementation (/octo:deliver)"},
{label: "Iterate on the implementation", description: "Make adjustments or handle edge cases"},
{label: "Run quality gates again", description: "Re-validate with updated code"},
{label: "Export the implementation", description: "Save a summary of what was built"},
{label: "Done for now", description: "I have what I need"}
]
}
]
})
Dispatches to the develop workflow via orchestrate.sh for the implementation phase.
xhigh for complex implementation and high for ordinary work.OCTOPUS_OPUS_MODE, OCTOPUS_OPUS_MODEL, and OCTOPUS_EFFORT_OVERRIDE.Just use natural language:
"Build a user authentication system"
"Implement OAuth 2.0 flow"
"Create a caching layer for the API"
The Develop phase of the Double Diamond methodology (divergent thinking for solutions):
Use develop when you need:
Develop is phase 3 of 4 in the embrace (full) workflow:
To run all 4 phases: /octo:embrace
npx claudepluginhub nyldn/claude-octopus --plugin octo/multi-workflowOrchestrates a 6-phase multi-model development workflow (research, ideation, planning, execution, optimization, review) using Codex for backend and Gemini for frontend collaboration.
/multi-workflowOrchestrates 6-phase multi-model development workflow (Research→Ideation→Plan→Execute→Optimize→Review), routing frontend tasks to Gemini and backend to Codex.
/implementImplements features with parallel subagents through multi-phase workflow: discovery, architecture, coding, testing, reflection, with effort scaling and resume support.
/developBuilds features via multi-phase Research, Plan, Implement, Review & Commit workflow with confidence scoring, validation gates, tests, and conventional commits.
/developImplements AL/BC solution from .dev/02-solution-plan.md using parallel AL developers and 4-specialist review team, producing reviewed code.
/developSpawns orchestrator subagent to autonomously implement ticket via triage-plan-code-review-QA-PR workflow, creates git worktree if needed, updates ticket status.