What problem does it solve? When adding or modifying any Copilot, agent, LLM, permission, sandbox, MCP, telemetry, or configuration control in VS Code, contributors must decide where the enterprise policy belongs—runtime managed settings, VS Code configuration policy, extension policy, or a split implementation—and follow the correct declaration, export, and testing procedure. ## Core Features & Use Cases - Policy Routing Decision Tree: A flowchart routes each control to the correct destination based on where the governed behavior is implemented, with dedicated guides for SDK/runtime, VS Code, extension, split, and legacy migration paths. - Managed Settings Reference: Documents the canonical dot-path bag, three delivery channels (native MDM, server, file-based) with per-key precedence, structured JSON-string encoding, and the managedSettingValue helper pattern. - Export and Testing Workflow: Prescribes npm run export-policy-data, the policyData.jsonc verification step, and local testing via the mock policy server. - Use Case: When adding a new enterprise control that disables a Copilot agent tool, use this Skill to determine it belongs in the runtime managed-settings schema, declare the key constant, attach it to a policy, and export the policy catalog correctly. ## Quick Start Ask the assistant to use the policy-and-managed-settings skill to decide where a new Copilot enterprise control should be implemented and walk through the required declaration and export steps.
