What problem does it solve? Adding an enterprise control for Copilot, agents, or VS Code requires choosing the correct policy destination—runtime managed settings, VS Code configuration policy, extension policy, or a split implementation—and following the right declaration, export, and testing procedure. Choosing the wrong channel leads to duplicated enforcement, silently ignored settings, or deprecated integration paths. ## Core Features & Use Cases - Policy destination routing: A decision flowchart routes any new Copilot/agent/LLM control to the SDK/runtime managed-settings contract, a VS Code configuration policy, an extension-provided setting policy, or a split runtime/editor control based on where the governed behavior is implemented. - Managed-settings implementation guidance: Detailed references cover declaring managedSettings keys on policies, structured (object/array) settings carried as JSON strings, per-key channel precedence (native MDM > server > file), and the policyReference mechanism for one policy governing many settings. - Export and testing procedures: Step-by-step instructions for running npm run export-policy-data, verifying policyData.jsonc, and testing locally with 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, then follow the SDK/runtime guide to declare the key, wire enforcement, and add tests. ## Quick Start Ask the Skill where a new enterprise control for a Copilot agent feature should be implemented and follow the routed guide to declare and export the policy.
