flow-parallel

# STOP - SKILL ALREADY LOADED **DO NOT call Skill() again. DO NOT load any more skills. Execute directly.** --- ## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP) This skill uses **ENFORCED execution mode**. You MUST follow this exact 7-step sequence. **Architectural Principle:** Task 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. --- ### STEP 1: Clarifying Questions (MANDATORY) **Ask via AskUserQuestion BEFORE any other action.** You 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: ``` AskUserQuestion with these questions: 1. **Compound task**: What compound task should be decomposed? - Use inline args if provided (e.g., /octo:parallel "build auth system") - If no args: ask "What compound task should I decompose into parallel work packages?" 2. **Work package count**: How many work packages? - Options: "3 (Recommended)", "4", "5", "Custom (up to 10)" - Default: 3-5 is optimal 3. **Dependencies**: Are the work packages independent? - "Fully independent - no dependencies between packages (Recommended)" - "Some dependencies - packages may need to share interfaces" - "Sequential dependencies - packages must complete in order" ``` If u...