Ships with octo. Installing the plugin gets this command.
⚡ How it fires
How this command gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/develop
👁️ Context preview
What this command does when you run it.
Development phase - Build solutions with multi-AI implementation and quality gates
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> Command definition
develop.md
---command: develop
description: "Development phase - Build solutions with multi-AI implementation and quality gates"
aliases:
- tangle
- build-phase
---# 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(skill: "octo:develop")` because it resolves back to this file and loops
- Using `Skill(skill: "flow-develop", ...)` because that internal name is not resolvable by the Skill tool
- Using the Agent tool, WebFetch, Read, or Grep as a substitute for multi-provider dispatch
- Skipping `orchestrate.sh` calls because "I can do this faster directly"
- Implementing the task using only Claude-native tools
**Multi-LLM orchestration is the purpose of this command.** If you execute using only Claude, you've violated the command's contract.
---
List available providers and mark missing providers as `(unavailable - skipping)`. If `OCTOPUS_COMPACT_BANNERS=true`, use this compact single-line format:
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
```
### Post-Completion — Interactive Next Steps
**CRITICAL: After the workflow completes, you MUST ask the user what to do next. Do NOT end the session silently.**
```javascript
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.**
### Model and Effort Policy
- For develop/tangle work on Opus 4.8, use `xhigh` for complex implementation and `high` for ordinary work.
- Fast Opus 4.8 mode is 2x standard cost ($10/$50 per MTok vs $5/$25 standard) and trades cost for lower latency. Legacy Opus 4.6 fast remains 6x standard cost.
- Default to Opus 4.8 standard mode for multi-phase workflows; use fast mode only for interactive single-shot requests when explicitly selected.
- Respect user overrides: `OCTOPUS_OPUS_MODE`, `OCTOPUS_OPUS_MODEL`, and `OCTOPUS_EFFORT_OVERRIDE`.
- Record durable project memory for autonomy mode, provider availability, frequently used commands, prior project context, and model preferences.
- If Claude Code dynamic workflows are available and the task is a huge single-Claude migration, prefer the native workflow path. Use Octopus develop when multi-provider implementation or validation is the value.
## Quick Usage
Just use natural language:
```
"Build a user authentication system"
"Implement OAuth 2.0 flow"
"Create a caching layer for the API"
```
## What Is Develop?
The **Develop** phase of the Double Diamond methodology (divergent thinking for solutions):
- Multiple implementation approaches via external CLI providers
