copilot-rollout-playbooklisted

# copilot-rollout-playbook A Category 3 ops tool. The user runs this against a target team and gets a tailored, sourced rollout plan ready to share with the team lead. Composes with `copilot-faq-answerer` for the policy answers stakeholders will ask during rollout, and with `objection-response-library` for the resistance points. ## When to use - A team lead requests Copilot rollout for their team. - Planning an org-wide expansion wave; need a template plan customized per BU. - Refreshing a stalled rollout — figure out which of the 5 phases the team is actually in. ## When NOT to use - General "should we adopt Copilot" question — that's a decision, not a rollout. - Specific config debugging (workflow won't trigger, content exclusion not enforcing) — those are `actions-workflow-hardener` / `ghas-config-reviewer`. - Cost modeling for the rollout — that's `copilot-metrics-analyzer`. ## Required inputs - **Team size** (devs). - **Language stack** — affects what models route per-feature and what training emphasizes. - **Current Copilot adoption state** — none / partial / org-wide. - **Business priorities** — feature velocity / quality / cost reduction / regulatory readiness. - **Regulatory exposure** — which regulated-data flows touch this team's repos (e.g., payments → PCI-DSS, customer data → privacy laws). ## Bank-specific constants (loaded from vault) The skill loads these from `vault/facts/copilot/` so plans reflect the org's current posture, not GitHub generic: - **