Skip to content
Automation
Command

/factory

[advanced] Dark Factory Mode - Spec-in, software-out autonomous pipeline

From plugin
octo
4.3k53 skills49 agents53 commands18 hooks
> /plugin marketplace add nyldn/claude-octopus

Command definition

factory.md
command: factory
disable-model-invocation: true
description: "[advanced] Dark Factory Mode - Spec-in, software-out autonomous pipeline"
aliases:
  - dark-factory
  - build-from-spec

Factory - Dark Factory Mode (v8.25.0)

INSTRUCTIONS FOR CLAUDE

MANDATORY COMPLIANCE — DO NOT SKIP

**When the user explicitly invokes `/octo:factory`, you MUST execute the orchestrated factory pipeline below.** You are PROHIBITED from replacing the pipeline with a direct Claude-only implementation.

When the user invokes this command (e.g., `/octo:factory --spec <path>`):

Step 1: Ask Clarifying Questions

**CRITICAL: Before starting the factory pipeline, use the AskUserQuestion tool to gather context:**

Ask 3 clarifying questions: 1. Spec path — Where is the NLSpec file? (provide path, or paste inline) 2. Satisfaction target — Accept spec default, or override? (Use spec default / Custom target 0.80-0.99) 3. Cost confirmation — Factory mode runs ~20-30 agent calls (~0.50-2.00 USD). Proceed? (Yes / Yes with --ci for non-interactive / No)

After receiving answers: validate spec path exists, set overrides, proceed.

Step 1.5: Ensure plugin root is resolvable (run via Bash tool)

OCTO_ROOT="${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_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 2: Check Provider Availability & Display Banner

Check via bash:

codex_available="Not installed"
if command -v codex >/dev/null 2>&1; then
  codex_available="Available"
fi

**MANDATORY: Check provider availability before displaying the banner:**

echo "PROVIDER_CHECK_START"
printf "codex:%s\n" "$(command -v codex >/dev/null 2>&1 && echo available || echo missing)"
printf "agy:%s\n" "$(command -v agy >/dev/null 2>&1 && echo available || echo missing)"
printf "perplexity:%s\n" "$([ -n "${PERPLEXITY_API_KEY:-}" ] && echo available || echo missing)"
printf "opencode:%s\n" "$(command -v opencode >/dev/null 2>&1 && echo available || echo missing)"
printf "copilot:%s\n" "$(command -v copilot >/dev/null 2>&1 && echo available || echo missing)"
printf "qwen:%s\n" "$(command -v qwen >/dev/null 2>&1 && echo available || echo missing)"
printf "ollama:%s\n" "$(command -v ollama >/dev/null 2>&1 && curl -sf http://localhost:11434/api/tags >/dev/null 2>&1 && echo available || echo missing)"
printf "openrouter:%s\n" "$([ -n "${OPENROUTER_API_KEY:-}" ] && echo available || echo missing)"
echo "PROVIDER_CHECK_END"

Render the factory 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.

status_cli() { command -v "${1}" >/dev/null 2>&1 && echo "Available ✓" || echo "Not installed ✗"; }
status_env() { [[ -n "${1:-}" ]] && echo "Configured ✓" || echo "Not configured ✗"; }
codex_status="$(status_cli codex)"
agy_status="$(status_cli agy)"
opencode_status="$(status_cli opencode)"
copilot_status="$(status_cli copilot)"
qwen_status="$(status_cli qwen)"
if command -v ollama >/dev/null 2>&1 && curl -sf http://localhost:11434/api/tags >/dev/null 2>&1; then ollama_status="Available ✓"; else ollama_status="Not installed ✗"; fi
perplexity_status="$(status_env "${PERPLEXITY_API_KEY:-}")"
cat <<BANNER
CLAUDE OCTOPUS ACTIVATED - Dark Factory Mode
Pipeline: Parse → Scenarios → Embrace → Holdout → Score → Report

Providers:
  🔴 Codex CLI: ${codex_status}
  🧭 Antigravity CLI: ${agy_status}
  🟤 OpenCode: ${opencode_status}
  🟢 Copilot CLI: ${copilot_status}
  🟠 Qwen CLI: ${qwen_status}
  ⚫ Ollama: ${ollama_status}
  🔵 Claude: Available ✓ - Orchestration, synthesis, satisfaction scoring
  🟣 Perplexity: ${perplexity_status}
BANNER

The rendered factory banner must look like this shape, with ACTUAL statuses:

CLAUDE OCTOPUS ACTIVATED - Dark Factory Mode
Pipeline: Parse → Scenarios → Embrace → Holdout → Score → Report

Providers:
  🔴 Codex CLI: [Available ✓ / Not installed ✗]
  🧭 Antigravity CLI: [Available ✓ / Not installed ✗]
  🟤 OpenCode: [Available ✓ / Not installed ✗]
  🟢 Copilot CLI: [Available ✓ / Not installed ✗]
  🟠 Qwen CLI: [Available ✓ / Not installed ✗]
  ⚫ Ollama: [Available ✓ / Not installed ✗]
  🔵 Claude: Available ✓ - Orchestration, synthesis, satisfaction scoring
  🟣 Perplexity: [Configured ✓ / Not configured ✗]

Spec: <spec-path>
Estimated cost: 0.50-2.00 USD (~20-30 agent calls)

**PROHIBITED: Displaying only Claude without listing all providers.** If no external providers are available, warn but proceed (Claude-only mode is supported).

EXECUTION MECHANISM — NON-NEGOTIABLE

**You MUST execute this command by calling `orchestrate.sh` as documented below. You are PROHIBITED from:**

  • ❌ Doing the work yourself using only Claude-native tools (Agent, Read, Grep, Write)
  • ❌ Using a single Claude subagent instead of multi-provider dispatch via orchestrate.sh
  • ❌ Skipping orchestrate.sh 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.

Step 3: Validate Spec

Read the spec file and verify it contains:

  • Purpose or description section
  • At least one behavior or requirement
  • Ideally: actors, constraints, acceptance criteria
Read more
@nyldn
Ships withocto

Every AI model has blind spots. Claude Octopus supports twelve external provider integrations — Codex, Antigravity CLI, Copilot, Qwen, Ollama, Perplexity, OpenRouter, OrcaRouter, OpenCode, Cursor CLI, Grok, and Kimi Code — alongside the built-in Claude Code

4.3k70 skills49 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
4.3k
Star history of nyldn/claude-octopus on GitHub, a chart by star-history.com

Other commands on octo.

auto

auto

Command

Smart router - Single entry point with natural language intent detection

@nyldn@nyldnInstall Command
brainstorm

brainstorm

Command

Start a creative thought partner brainstorming session

@nyldn@nyldnInstall Command
budget-mode

budget-mode

Command

Switch Octopus model routing to the configured budget tier

@nyldn@nyldnInstall Command
careful

careful

Command

[advanced] Activate destructive command warnings for the session

@nyldn@nyldnInstall Command
costs

costs

Command

[advanced] Compatibility view of the deterministic Octopus usage report

@nyldn@nyldnInstall Command
council

council

Command

Multi-LLM council for advice, decision support, implementation plans, and gated implementation

@nyldn@nyldnInstall Command

More commands from other plugins.

plan

plan

Command

Plan n8n Linear ticket implementation

n8n11d209k
@n8n-io@n8n-ioInstall Command
setup

setup

Command

One-time setup after installing ARIS as a Claude Code plugin — registers the Codex reviewer MCP server from the plugin directory…

aris12d18k
@wanshuiyin@wanshuiyinInstall Command
agent
Auto-invoked

agent

Command

name: sc:agent description: SC Agent — session controller that orchestrates investigation, implementation, and review category:…

@galaxy-dawn@galaxy-dawnInstall Command