What problem does it solve? Adding an enterprise control for Copilot, agents, or VS Code involves choosing between runtime managed settings, VS Code configuration policy, extension policy, or a split implementation, and picking the wrong channel creates duplicated enforcement or silently ignored settings. ## Core Features & Use Cases - Decision routing: A flowchart routes any new 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 projection checklist. - Policy export workflow: Prescribes the required npm run export-policy-data procedure so policyData.jsonc stays consistent and the blocking integration test passes. - Use Case: When adding a new Copilot permission control, use this Skill to determine it belongs in the runtime managed-settings schema, then follow the projection checklist to declare the key constant, attach it to a policy, and export the policy catalog. ## Quick Start Ask the Skill where a new enterprise control for a Copilot agent feature should be implemented and follow the routed guide.
