master-orchestrator-requires-explicit-not-covered-section
Without a clearly stated refusal boundary, master-orchestrator attempts to route requests it has no specialist for (mobile, ML/AI, real-time streaming, Web3, game dev, browser extensions, ETL pipelines, embedded systems, legacy COBOL). Added an ‘Explicitly Not Covered’ section with a refusal template. Any orchestrator skill that handles routing must explicitly enumerate out-of-scope domains to prevent confident misdelegation.