flow-parallel

1> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
2> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
3> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
4> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
5 
6 
7# STOP - SKILL ALREADY LOADED
8 
9**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**
10 
11 
12## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)
13 
14This skill uses **ENFORCED execution mode**. You MUST follow this exact 7-step sequence.
15 
16**Architectural Principle:** host subagent tool subagents do NOT load plugins. Independent `claude -p` processes DO. This skill spawns independent `claude -p` processes so each work package gets the full Octopus plugin, its own Double Diamond, agents, and quality gates.
17 
18 
19### STEP 1: Clarifying Questions (MANDATORY)
20 
21**Ask via AskUserQuestion BEFORE any other action.**
22 
23You MUST gather these inputs from the user — without scope, count, and dependency answers, the decomposition will be generic and produce overlapping work packages that cause merge conflicts:
24 
25```
26AskUserQuestion with these questions:
27 
281. **Compound task**: What compound task should be decomposed?
29   - Use inline args if provided (e.g., /octo:parallel "build auth system")
30   - If no args: ask "What compound task should I decompose into parallel work packages?"
31…