run-orchestratorlisted

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Run Orchestrator For complex features / multi-file changes requiring TDD. NOT for: bug fixes (use the `bugfix-quick` **skill** via the Skill tool — it is NOT an agent), quick edits (direct). ## Step 0 — Escalation Check (precondition, v3.7.2+) Before creating run-state.json, screen the task description for project-level scope via the bridge heuristic in `rules/workflow/run-plan-bridge.md`. The 8-trigger rubric (multi_feature, multi_week, shipping_scope, scale_words, cross_session, user_explicit, word_count, scope_verbs) sums to a weight; if weight ≥ 3 AND no plan tree exists (`.claude/plans/active.json` missing), emit this 3-option prompt: ``` Your task scores ≥3 on the escalation heuristic — multi-feature / multi-session scope. Options: plan — bootstrap /aura-frog:plan first (writes pending-plan-bootstrap.json) deep — proceed with normal Deep flow (escalation_declined: true recorded) details — show breakdown of which signals fired, re-ask ``` **Honour the answer:** - `plan` → write `.claude/cache/pending-plan-bootstrap.json` (schema below) and invoke `/aura-frog:plan`. Do NOT proceed to Step 0b until the plan returns. - `deep` (or legacy alias `proceed`) → set `escalati