---
name: scale-exec-pitch
description: Turns the charter, friction map, capability decision, and pilot into a 60-second leadership pitch plus a one-page memo the sponsor can forward. Use when the user says "pitch this to my exec team", "60 second version", "board update", "explain the pilot to my CEO", "one pager for leadership", or after the pilot has a week of data.
---

# scale-exec-pitch

Produce `artifacts/scale-pitch.md`. Problem, number, plan, team, timeline, risk, ask. Sixty seconds, then a page.

## 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`: `<date> | <skill> | <produced> | <human changed> | <open question>`.

## Prerequisites
- `artifacts/scale-charter.md`, `artifacts/scale-friction-map.md`, `artifacts/scale-capability-decision.md`, `artifacts/scale-pilot.md`.
Cold-start: "In five lines: the problem with a number, what you're trying, with whom, by when, and what you need from leadership." Continue; mark the pitch draft (fast path).

## Step 1: Sixty seconds
Write it to be spoken in under a minute:
- The problem and what it costs (from the friction map)
- The number we're moving (from the charter)
- What we're doing and with whom (from the pilot)
- When we'll know (stop trigger date, end date)
- The one risk and how we've bounded it (guardrails, cancel trigger)
- The ask (time protection, budget, a decision)

## Step 2: The page
One page under the same headings with the evidence: baseline, target, hypothesis, success criteria, team, weekly control, reversal trigger. Pull real numbers from the artifacts; never invent.

## Step 3: Drip version
A three-line weekly update template for `~~chat` or `~~email`: what we learned, what moved, what we need.

## Step 4: Write
Save the file. Update `INDEX.md`.

## Hand off
Say: "Module 4 is running. When the pilot has data, install `scale-evolve / os-learn` and run `scale-exec-dashboard`."