executelisted

# Execute — Orchestrated Task Engine Decompose a goal into atomic tasks, plan dependencies, select optimal tools, and execute with maximum parallelism. ## Pre-Flight Gate Activation is decided by the frontmatter description alone — this file is read only AFTER the skill has been selected. Nothing here can prevent over-triggering, so this gate is a **post-selection redirect**, not a filter. **Before proceeding, check the ABORT condition below. If it holds, STOP, say in one line that it fired, and just do the task.** Being invoked — including a literal `/execute` or "orchestrate this" — does NOT override an ABORT: the phrasing that selected this skill is not evidence the goal is multi-step. - Run the 6-phase protocol only when the goal is genuinely multi-step — ≥3 atomic tasks, spans multiple files/tools, or benefits from parallel batches. - ABORT (do it directly): a single edit, a one-file change, a question, or anything one tool call resolves. ## Protocol Process every `/execute` invocation through these 6 phases in strict order. Never skip a phase. Gate each phase: do not advance until the current phase is complete. ### Phase 1: ANALYZE Understand the goal before decomposing it. 1. Parse `$ARGUMENTS` as the goal statement 2. Identify the goal type (feature, bugfix, refactor, research, migration, infrastructure, other) 3. Explore the codebase to understand current state — use Glob, Grep, Read, or the Explore agent for broad searches 4. Check existing skills, memory