architect-orchestratorlisted

# Adaptive orchestration The primary AI owns decomposition, judgment, integration and the user-facing answer. This skill is optional JIT guidance when delegation, independent alternatives, graph ownership or bounded execution materially improves the task. Agent roles are capabilities, not a mandatory org chart. Do not require an Architect/Supervisor/Worker hierarchy for work that does not benefit from it. ## Before topology The primary AI should already have or construct a reviewed `TASK_DECISION` covering the material outcome, unresolved unknowns, relevant packs, selected skills/references/tools, complexity, risk, topology, plan and verification. Before delegating: 1. inspect project/user constraints; 2. separate the desired outcome from a merely suggested implementation method; 3. challenge a materially weaker method and preserve the user's final safe discretionary choice; 4. ensure selected skill bodies/references are actually available JIT; 5. compare genuinely different alternatives before expensive-to-reverse structural commitment when that comparison has value; 6. choose topology from dependencies, ownership and useful independence; 7. instantiate deterministic Loop/Graph contracts for executable work when their enforcement is useful. Do not ask users to choose internal pack names, worker counts or topology jargon. ## Why delegate Useful reasons include: - large independent reading/research sets; - distinct implementation packages or ownership boundaries; - d