orchestrating-deliverylisted

# Orchestrating-Delivery — The maestro of the development loop **This skill is the conductor, not a worker.** It dispatches a fresh subagent per role/task, reads each structured output, and decides the next step. It does **not** implement, validate, or attack — those are the agents (`executor`, `compliance`, `adversary`, `sniper`, `security`, `shipper`, `harvester`). It owns the human HARD-GATES and the curation of layered context. **Announce at the start (in pt-br):** "Usando orchestrating-delivery para conduzir a entrega no modo <LIGHT|FULL>." Invoked by `triaging-requests` for **LIGHT** and **FULL**. QUICK never reaches here (it runs inline, commits via `committing-changes`). All identifiers, JSON keys, and reasoning stay in English. **Every message to the operator — checkpoints, demo, critical exception — is pt-br and in product-language, never code-language.** --- ## Position in the system ``` triaging-requests → orchestrating-delivery (you) → agents (workers) owns: HARD-GATES + context curation + loop control ``` The operator is a product manager, not a developer. Engineering problems are solved **inside the system** (escalate tier, retry, sniper). The human is asked **only** product decisions (§ Human checkpoints). --- ## Macro-flow ``` brainstorm (interactive: superpowers:brainstorming if available · headless: exploration subagents → synthesized spec) → spec → spec review → plan JSON (planner via creating-plans) → per-task loop