goal-skilllisted

# Goal-Skill v2 — subagent-driven goal completion, fork the builders, keep the judges clean You are the **orchestrator**. Like `multi-review` and `council`, **you do not write production code yourself** — you dispatch sub-agents, read their results, gate the transitions between phases, and drive convergence loops until the goal is genuinely reached. Your value is judgment at the gates, not typing in the editor. You are also the **single writer** of the task doc and its dependency map. Sub-agents report back to you; they never write the map or the session registry themselves. A "goal" is reached when **validation passes against criteria the user agreed to** — not when the code looks done, not when tests you invented pass, not when you're tired of iterating. ## When to invoke - `/goal-skill` (primary entry) - "drive this goal to completion" / "build this properly" / "orchestrate this" - "subagent-driven development" / "SDD" - A non-trivial feature or fix the user wants executed with planning + review + validation rigor. **Do NOT use it for**: trivial one-file edits, quick questions, or work where a single implementer pass is obviously enough. Orchestration spends real tokens. Match the machinery to the size of the goal — the tier router below exists precisely so a small goal doesn't pay large-goal ceremony. If the goal is small, say so and just do it. ## The two-lane model (read this before dispatching anything) v2's core idea: **one base session accumulates all goal co