---
name: scale-opportunity-matrix
description: Ranks friction points on impact and feasibility into Plan / Quick win / Reconsider / Skip so the user knows what to fix first. Use when the user says "what should we fix first", "prioritize these problems", "rank the friction", "impact vs effort", "opportunity matrix", or after scale-friction-map completes.
---

# scale-opportunity-matrix

Produce `artifacts/scale-opportunity-matrix.md`. Everyone has more friction than time. This picks.

## 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-friction-map.md`.
Cold-start: "List the three to six biggest time sinks or breakdowns in your revenue process, one line each." Write them as a minimal friction list and continue.

## Step 1: Score every stall
For each friction point: Impact 1 to 10 (dollar cost from the map, or revenue exposure) and Feasibility 1 to 10 (data exists, system is accessible, owner is willing, no legal or security block). Ask the user to challenge any score; write down why they changed it.

## Step 2: Place in quadrants
- Impact ≥7, Feasibility ≥7: Plan (do first)
- Impact ≥7, Feasibility <7: Reconsider (fix readiness, then do)
- Impact <7, Feasibility ≥7: Quick win (do if cheap)
- Both <7: Skip

## Step 3: Check against the charter
The top Plan item must connect to the Module 1 root cause. If it doesn't, say so and ask which is wrong: the map or the charter.

## Step 4: Write
Write the matrix and a one-line recommendation: "Take <friction> into Module 3." Update `INDEX.md`.

## Hand off
Say: "Before we pick technology, run `scale-data-inventory` on the systems that friction touches. Then `os-win-loss-extract`."