--- name: scale-coe-charter description: Drafts the AI Center of Excellence charter with a technology co-chair, a business co-chair, named roles by title, an executive sponsor, cadence, and decision rights, sized to the company's stage. Use when the user says "who should own AI", "center of excellence", "AI committee", "CoE", "our sponsor is HR, is that right", "tiger team to permanent", or after scale-operating-calendar. --- # scale-coe-charter Produce `artifacts/scale-coe.md`. Two co-chairs, one technology and one business. Neither works alone. ## Preflight (every run) 1. Confirm `GTM-AI-OS/` is accessible. If not: "I need access to your GTM-AI-OS folder. Select it in Cowork's folder picker, or run `os-install` from the core plugin." Stop until it is. 2. Read `CLAUDE.md`, `INDEX.md`, and the last 20 lines of `signals/log.md`. 3. Check the prerequisites below. For anything missing, ask the cold-start questions and offer: (a) run the earlier skill now, or (b) fast path: answer the questions and this skill writes a minimal version of the missing artifact marked `status: draft (fast path)`. 4. On finish, update the artifact row in `INDEX.md` and append one line to `signals/log.md`: ` | | | | `. ## Prerequisites - `artifacts/scale-pilot.md` (the tiger team is the seed of the CoE). Cold-start: "Who ran your AI pilot, who sponsored it, and how big is the company?" Continue. ## Step 1: Size it Ask company size and regulation level. Startup or unregulated: a revenue-org CoE of three to five people. Mid-size or regulated: the full model below. ## Step 2: The structure - Executive sponsor: as high as possible (CEO, CRO, or CTO). If the sponsor is HR, say plainly: HR belongs on the core team, not in the chair, because the work is business outcomes and technology, and prioritization stalls otherwise. - Technology co-chair (owns speed, build, safety, security) and business co-chair (owns ROI, adoption, prioritization). - Core team by title: legal, security, training and enablement, GTM (sales, marketing, CS), product and engineering, RevOps as data and systems steward, plus any industry-required role (e.g. medical, compliance). Fill names where the user has them; titles where they don't. ## Step 3: Charter Purpose (translate AI into measurable business outcomes safely and repeatably), decision rights (what the CoE approves, what teams can do alone), intake (how a use case gets proposed and prioritized), budget path, and the relationship to tiger teams (CoE resources them; they run the pilots). ## Step 4: Cadence Biweekly to start, with two standing agenda items: the prioritized use-case list and performance of what's already shipped. Add to the operating calendar. ## Step 5: The 90-day and 12-month view Ninety days: name the pseudo AI head, formalize the tiger team, run intake once. Twelve months: the structure that makes this permanent, including whether a dedicated forward-deployed pod (GTM engineer, agent engineer) reports into the CRO, RevOps, or the CTO. Don't deploy that pod until the foundations exist. ## Step 6: Write Write the charter with a role table. Update `INDEX.md`. ## Hand off Say: "Write the rules the CoE will enforce. Run `scale-governance`."