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/embrace
👁️ Context preview
What this command does when you run it.
Full Double Diamond workflow - Research → Define → Develop → Deliver
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> Command definition
embrace.md
---command: embrace
description: "Full Double Diamond workflow - Research → Define → Develop → Deliver"
aliases:
- full-cycle
- complete-workflow
---# Embrace - Complete Double Diamond Workflow
**Your first output line MUST be:** `🐙 Octopus Embrace`
## MANDATORY COMPLIANCE — DO NOT SKIP
**When the user invokes `/octo:embrace`, you MUST execute the full multi-LLM workflow below. You are PROHIBITED from:**
- Deciding the task is "too simple" for the workflow
- Doing the task directly instead of running the phases
- Skipping phases because you judge them unnecessary
- Substituting your own approach for the structured workflow
**The user chose `/octo:embrace` deliberately.** Respect that choice.
## EXECUTION MECHANISM — NON-NEGOTIABLE
**Each phase MUST be executed through the `orchestrate.sh` entrypoint. Direct Skill calls for the workflow phases are not permitted because they can recursively reload command instructions. You are PROHIBITED from:**
- Using the Agent tool to do research yourself instead of running the discovery phase
- Using WebFetch/Read/Grep as a substitute for multi-provider research
- Implementing code directly instead of running the develop phase
- Using a single code-reviewer agent instead of running the deliver phase
- Skipping `orchestrate.sh` calls because "I can do this faster directly"
**The ENTIRE POINT of `/octo:embrace` is multi-LLM orchestration.** If you execute phases using only Claude-native tools (Agent, WebFetch, Write, Edit), you have violated the command's purpose even if you followed the phase structure.
**Self-check after completion:** You should be able to list the `orchestrate.sh` commands you ran. If you used only Claude-native tools, you executed incorrectly.
---
## Step 1: Ask Clarifying Questions
```javascript
AskUserQuestion({
questions: [
{
question: "What's the scope of this project?",
header: "Scope",
multiSelect: false,
options: [
{label: "Small feature", description: "Single component or small addition"},
{label: "Medium feature", description: "Multiple components or moderate complexity"},
{label: "Large feature", description: "System-wide changes or new subsystem"},
{label: "Full system", description: "Complete application or major architecture"}
]
},
{
question: "What areas require the most attention?",
header: "Focus Areas",
multiSelect: true,
options: [
{label: "Architecture design", description: "System structure and design patterns"},
{label: "Security", description: "Authentication, authorization, data protection"},
{label: "User experience", description: "UI/UX and usability"}
]
},
{
question: "What's your preferred level of autonomy?",
header: "Autonomy",
multiSelect: false,
options: [
{label: "Supervised (default)", description: "Review and approve after each phase"},
{label: "Semi-autonomous", description: "Only intervene if quality gates fail"},
{label: "Autonomous", description: "Run all 4 phases automatically"},
{label: "Manual", description: "I'll guide each step explicitly"}
]
},
{
question: "Should critical decisions be stress-tested with a Multi-LLM debate?",
header: "Multi-LLM Debate Gates",
multiSelect: false,
options: [
{label: "Yes — debate at Define→Develop gate", description: "Recommended for Large/Full scope"},
{label: "Yes — debate at both gates", description: "Maximum rigor, uses external API credits"},
{label: "No — skip debates", description: "Standard workflow without debate checkpoints"},
{label: "Only if disagreement detected", description: "Auto-trigger when providers diverge"}
]
}
]
})
```
After receiving answers, incorporate them into all subsequent phase invocations — use the scope to calibrate research depth, focus areas to weight provider perspectives, autonomy level to control phase transitions, and debate preference to gate handoffs.
Normalize the debate preference immediately:
- `DEBATE_GATES=define` for "Yes — debate at Define→Develop gate"
- `DEBATE_GATES=both` for "Yes — debate at both gates"
- `DEBATE_GATES=none` for "No — skip debates"
- `DEBATE_GATES=auto` for "Only if disagreement detected"
**Gate ledger invariant:** if `DEBATE_GATES=define`, a `embrace-gate-define-develop-*.md` artifact from the current run MUST exist before Phase 3 starts. If `DEBATE_GATES=both`, both `embrace-gate-define-develop-*.md` and `embrace-gate-develop-deliver-*.md` artifacts from the current run MUST exist before their next phases. Autonomy mode does not waive requested gates. If a requested gate command fails or produces no artifact, STOP and report the failed gate instead of continuing.
### Remote/Cloud Defaults
If `CLAUDE_CODE_REMOTE=true` or `OCTOPUS_REMOTE_SESSION=true`, do not block on clarifying questions. Use these defaults unless the user's prompt says otherwise:
- scope: infer from the prompt
- focus: all relevant areas
- autonomy: autonomous
- debate gates: only if provider disagreement is detected
Plan locally first, then run the approved `/octo:embrace` prompt in the hosted or remote-control session with `OCTOPUS_REMOTE_SESSION=true` set in that environment.
Render the provider banner from actual provider checks. Do not hand-write or summarize this banner; run this block and display its output exactly. The output MUST include the Antigravity line even when `agy` is missing.
**CRITICAL: Each phase MUST run through `orchestrate.sh`. Do not invoke `/octo:discover`, `/octo:define`, `/octo:develop`, or `/octo:deliver` via Skill calls inside this command; direct phase dispatch prevents recursive command loading.**
**CRITICAL: Run every orchestrate.sh command from the user's project directory. Do NOT `cd` into the plugin first — dispatched providers (codex workdir, gemini workspace) sandbox themselves to the invoking directory, and a plugin cwd makes every provider unable to read the user's project files. If the prompt references files outside the project (e.g. /tmp), pass `-d <dir>` or set `OCTOPUS_GEMINI_INCLUDE_DIRS`.**
3. Verify `~/.claude-octopus/results/embrace-gate-define-develop-*.md` exists for this run before Phase 3. If the command fails or no artifact exists, STOP.
4. If risks surface and autonomy is supervised/manual, present via AskUserQuestion:
```javascript
AskUserQuestion({
questions: [{
question: "The debate gate surfaced concerns. How should we proceed?",
header: "Debate Gate",
multiSelect: false,
options: [
{label: "Proceed anyway", description: "Accept risks and continue to Develop"},
{label: "Revise approach", description: "Adjust plan based on debate findings"},
{label: "Run deeper debate", description: "Thorough 3-round debate before deciding"},
{label: "Stop and review", description: "Pause for manual review"}
Verify `~/.claude-octopus/results/embrace-gate-develop-deliver-*.md` exists for this run before Phase 4. If the command fails or no artifact exists, STOP. In autonomous mode, continue only after the gate artifact exists; do not silently skip this gate.
