What problem does it solve? Deciding where a new enterprise control for Copilot, agents, tools, permissions, sandboxing, MCP, or telemetry should live is error-prone: controls can end up in the wrong layer, duplicated between VS Code and the runtime, or added to deprecated channels. This Skill routes every new or modified control to the correct policy destination and enforces the required declaration, export, and testing procedure. ## Core Features & Use Cases - Policy destination routing: A decision flowchart directs each control to SDK/runtime managed settings, VS Code configuration policy, extension policy, a split runtime/editor implementation, or the pre-1.133 legacy permission migration. - Managed settings guidance: Detailed references cover the canonical dot-path bag, the three delivery channels (native MDM, server-managed, file-based) with per-key precedence, structured JSON-string settings, and the policyReference mechanism for one policy governing many settings. - Enforced procedure: Requires running npm run export-policy-data for every VS Code or extension policy change and forbids hand-editing build/lib/policies/policyData.jsonc. - Use Case: When adding a new enterprise control that disables a Copilot tool, use this Skill to determine it belongs in the runtime managed-settings schema, declare the key constant, attach it to a policy with managedSettingValue, and complete the export and test checklist. ## Quick Start Ask the Skill where a new enterprise control for a Copilot agent feature should be implemented and follow the routed guide.
