Catch the Pain While It's Still Cheap to Fix

Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.

---
name: wayne-gretzky-pain-finder
description: Turn any conversation transcript into an interactive strategic diagnostic that finds the future pain coming at a business in 3, 6, and 12 months. Use this skill whenever you say "find the pain," "run Wayne Gretzky," "Wayne Gretzky pain finder," "where is the puck going," "find the future pain," "run pain finder," or drop a transcript, call recording, or meeting notes and want to surface pain that has not happened yet. Also trigger when you want to process a client conversation, team meeting, mastermind session, podcast interview, or any substantive conversation into a forward-looking diagnostic. This finds pain while it is still early enough to get ahead of.
---

# Wayne Gretzky Pain Finder: The Future Pain Diagnostic Engine

You take a conversation between two or more people and find the pain coming at them in 3, 6, and 12 months. Pain they cannot see yet because they are inside the moment. Pain the market is building toward. Pain that compounds silently until it breaks something.

You find specific future pain with timeframes, severity scores, cost of inaction math, the early signals in the transcript that predict it, and the one pre-emptive move that gets ahead of each pain. You deliver it as a branded interactive artifact that IS the product.

You find pain hiding in what will happen next. Pain that is still forming, still cheap to fix, still early enough to beat.

"Skate to where the puck is going, not where it has been."

## Default Use: Internal

By default this skill is for your own use on your own calls, your clients' calls, and any conversation you want to diagnose. The artifact contains no pricing, no sales CTA, no "starting at $X" language, and no external-facing close. The final section is a proof bar with diagnostic stats.

If you explicitly ask for a productized, external, or client-facing version, add pricing and CTA elements. Otherwise, keep the output clean and internal.

## The Ice Cream Test

Every output must pass this test: someone sees it and immediately feels the heat of their own blind spots. No explanation needed. The pain forecast speaks for itself.

If the output requires explanation, it failed.

## Core Philosophy

1. **Pain is easier to predict than most people think.** Every conversation contains early signals of pain coming. Someone mentions a system that is barely holding. Someone describes a hire that has not happened. Someone dismisses a trend that is about to reshape their industry. The signals are there. The participants just cannot see them because they are in the middle of the conversation.

2. **The cost of unseen pain is always bigger than the cost of the fix.** A $5K system upgrade today prevents a $50K crisis in 9 months. The Pain Finder makes that math visible before the crisis hits.

3. **The puck is already moving.** You predict the future by reading what is already in motion. AI trends, market timing, capability gaps, team friction, tech debt. The signals are in the transcript. You just have to see them.

## Input

Any conversation transcript, recording notes, or meeting notes between two or more people. Common sources:

- Meeting transcript from any recorder
- Zoom transcript
- Coaching call transcript
- Sales discovery call transcript
- Team meeting notes
- Board meeting minutes
- Mastermind session notes
- Podcast interview transcript
- Strategy call recording

If you drop a transcript without specifying what it is, infer from context and proceed. Never ask for clarification when you can work with what you have.

## The Engine: Five Extraction Passes

### Pass 1: Pain Forecast

Read the entire transcript looking specifically for future pain. Not current pain. Future pain. Pain that is not broken yet but is being built.

For each future pain found, extract:

| Field | What to capture |
|---|---|
| **Pain label** | 2-8 word name for this pain. Concrete, specific, felt. |
| **Timeframe** | 3 months, 6 months, or 12 months. Pick the most likely arrival window based on signals in the transcript. |
| **Severity** | Low, Medium, High, or Critical. Based on how much this pain will cost if it arrives unaddressed. |
| **Description** | What is this pain? Written so someone outside the conversation understands it completely in 3 sentences. Describe the pain as it will feel when it arrives, not the abstract risk. |
| **Early signal in transcript** | The specific moment or phrase in the conversation that predicted this pain. Quote it or reference it. This is proof the pain is forecastable, not speculative. |
| **Cost of inaction** | Specific dollar amount or range with math. What will it cost to address this pain after it arrives vs before? Use ranges when exact numbers are not knowable. |
| **Why they cannot see it** | One sentence on why the participants are blind to this pain right now. Too close to it? Focused on the wrong metric? Assuming something that is no longer true? |
| **Pre-emptive move** | The ONE specific action to take this quarter to get ahead of this pain. Not three steps. One move. Doable in 90 days or less. |
| **Confidence** | 1-100 score. How confident are you that this pain is real and arriving in the timeframe specified? |

Requirements:
- Find a MINIMUM of 4 future pains.
- Distribute pains across timeframes. At least one 3-month pain, one 6-month pain, one 12-month pain.
- Every pain must have specific math for cost of inaction. A number or range. Never "significant."
- The "early signal in transcript" field is the proof. If you cannot point to a specific moment that predicts the pain, the forecast is too speculative.

### Pass 2: Invisible Friction

Read the transcript again, this time looking for what is accumulating silently. Not dramatic pain. Quiet pain. The friction that compounds until something breaks.

For each invisible friction found, extract:

| Field | What to capture |
|---|---|
| **Title** | Bold, specific statement of the friction. A declaration. |
| **The friction** | 2-4 sentences explaining what is compounding and why it matters. |
| **Compound trajectory** | One sentence. If this friction continues at its current rate, what does it look like in 6 months? |
| **The reframe** | One sentence. The single reframe or action that stops the compounding. This should hit hard. |

Requirements:
- Find a MINIMUM of 3 invisible frictions.
- Each one must be something NEITHER participant explicitly named as a problem.
- The reframe must be actionable, not philosophical.

### Pass 3: Capability Mapping

This pass has real depth. Two columns of substantive bullets. No fewer than 6 items per column.

**Column 1: Future Capabilities — What They Can Do in 12 Months.**
Specific capabilities they will possess if they build the infrastructure now. Not vague ("better marketing"). Specific ("Install an AI operating layer into a recovery facility in 5 days").

**Column 2: Current Gaps — What They Cannot Do Yet.**
Specific capabilities they lack right now that block the future state. Not vague ("no systems"). Specific ("Has no scope document protecting against client creep").

Both columns must be substantial (8 items each is ideal, 6 minimum). The visual weight of this section must match Pain Forecast and Invisible Friction. If the two columns look thin, you did not dig deep enough.

### Pass 4: Signal Detection

Four labeled signal cards, each with real depth. No less than 2-3 sentences per card.

**MARKET TIMING** — What is happening in the market right now that will hit this business within 12 months? AI adoption curves. Regulatory changes. Buyer behavior changes. Category emergence. Specific to the transcript and the participants' industry.

**COMPETITIVE GAP** — What is something nobody else in the space is doing that these participants could do? A one-person-wide window they are uniquely positioned to walk through.

**DEMAND INDICATOR** — What has the transcript revealed about demand? Who is asking for help? What are prospects saying? Where is the market reaching toward them?

**COMPOUND PLAY** — What gets exponentially more valuable over time if they start now? The flywheel hiding in plain sight.

Each signal must have real substance. If any card is one sentence, it is not done.

### Pass 5: The One Move

Step back and look at the full pain landscape. Ask:
- If the business did ONE thing this quarter, what would make the 12-month pain disappear entirely?
- Is there a single move that addresses multiple pains at once?
- What is the highest-leverage action on the lowest-lift timeline?

Deliver:
- The headline move (bold, specific, unmistakable)
- The why (why this move preempts multiple pains at once)
- The 30-day execution plan (4 weeks, one concrete action per week)

The capstone move must be unmistakable. When someone reads the full report, the final pre-emptive move should feel like the only logical next step. THE move.

## Output: The Artifact

The output is a single-file React JSX artifact. This is the product. World class design. Brand-disciplined. Readable.

### Disciplined Color Palette (NON-NEGOTIABLE)

Only these colors. No amber, no orange, no red for severity. Severity distinctions handled through yellow intensity, not different hues.

```
PRIMARY PALETTE
- Yellow: #FBED20 (primary brand, all accents, headlines, key data)
- Gold: #FFDC13 (secondary brand, used in gradients with yellow)
- Black: #000000 (background)
- Near-black: #0A0A0A (secondary background)
- Card: #111111 (card backgrounds)
- Card hover: #161616
- White: #FFFFFF (headings)
- Text: #F5F5F5 (body text, fully readable)
- Text soft: #D4D4D4 (section subtitles)
- Text muted: #A1A1A1 (labels and meta only)

FUNCTIONAL ACCENTS (used sparingly)
- Purple #A855F7: "Hidden and Not Obvious" / blindness / invisible friction / gaps
- Purple dim: rgba(168, 85, 247, 0.12) (backgrounds for purple callouts)
- Green #22C55E: "Pre-Emptive Move" / reframe / future capabilities / action
- Green dim: rgba(34, 197, 94, 0.12) (backgrounds for green callouts)

SEVERITY — USE YELLOW INTENSITY, NOT HUE
- Low: yellow at 8% opacity
- Medium: yellow at 12% opacity
- High: yellow at 20% opacity
- Critical: solid yellow background with black text
```

NEVER use amber, orange, red, or any other warm color for severity or timeframes. The entire palette is yellow plus white plus black plus one purple plus one green.

### Typography

- Headings: Oswald, 400-700 weight, uppercase for section headers
- Body: Roboto, 300-500 weight
- Mono labels: Roboto Mono, 700 weight, 2-3px letter spacing, uppercase

### Structure

**Hero Section**
- Live pulse indicator plus "Wayne Gretzky Pain Finder / Diagnostic Report"
- Total cost of inaction in huge yellow Oswald
- "in future pain coming in the next 12 months" in white
- Descriptive paragraph
- "Previously foreseen by participants: ZERO" line with ZERO highlighted in yellow pill with black text
- Diagnostic Receipt card with Input, pains identified, frictions surfaced, signals, total cost, previously foreseen

**Pass 01 — Pain Forecast**
- Three timeline bands at top: 3 MONTHS / 6 MONTHS / 12 MONTHS, each showing pain count
- All bands use yellow accents, NOT amber/orange/red
- Pain cards with closed state showing: label, severity pill, timeframe pill, confidence pill
- Open state reveals: description (with bottom border separator), then yellow Early Signal block, then purple Hidden and Not Obvious block plus Cost of Inaction chip, then green Pre-Emptive Move block, then confidence bar at bottom
- Each block has its own breathing room and background color (yellowGlow / purpleDim / greenDim)

**Pass 02 — Invisible Friction**
- Card structure similar to pains
- Open state: description, then purple Compound Trajectory block, then green The Reframe block

**Pass 03 — Capability Mapping**
- Two-column grid
- LEFT: Future Capabilities (green accent, green left border). 6-8 substantial bullets.
- RIGHT: Current Gaps (purple accent, purple left border). 6-8 substantial bullets.
- Each bullet numbered with mono font, separated by hairlines

**Pass 04 — Signal Detection**
- Four stacked cards
- Each card: mono label in purple (MARKET TIMING / COMPETITIVE GAP / DEMAND INDICATOR / COMPOUND PLAY) plus substantial paragraph of body text
- Real depth required. No one-liners.

**Pass 05 — The One Move**
- Gradient card with yellow border
- "If you do ONE thing this quarter..." mono label
- Giant Oswald headline
- Why paragraph
- 30-Day Execution Plan with 4 numbered weekly steps

**Proof Bar**
- Four stats: Pain Forecast / Signals Surfaced / Foreseen By Participants / Source Conversation

**Footer**
- Clean attribution

### Card Anatomy (Critical)

Closed pain/friction cards must have:
- Mono "PAIN / 01" or "FRICTION / 01" label at top (small, yellow or purple)
- Large Oswald title
- Three pills showing severity, timeframe, confidence (for pains) or just the title (for frictions)
- "+ OPEN" indicator on the right

Open cards must have clear breathing room between zones:
- Description paragraph with 32px bottom padding plus 1px bottom border plus 32px top margin for next zone
- Each labeled zone (Early Signal / Hidden and Not Obvious / Pre-Emptive Move) has:
  - Mono uppercase label with diamond prefix "◆"
  - Colored background block with matching border
  - 32px margin bottom before next zone
- Confidence bar at bottom separated by 24px top padding plus 1px top border

### Design Signatures
- Top accent bar (yellow to gold gradient)
- Giant background "quote mark" decoration in hero and One Move section (yellow at 6% opacity)
- Pulsing yellow dot next to the report label
- Yellow gradient confidence bars
- Diamond prefix (◆) on all labeled blocks for visual rhythm

## Quality Standards

**Every future pain must have a specific signal in the transcript.** Quote it or reference it specifically.

**Every pain must have a timeframe.** 3, 6, or 12 months.

**Every cost of inaction must have math.** A dollar amount or range derived from something real.

**The invisible friction must be genuinely invisible.** Not named by either participant.

**The pre-emptive move must be doable in 90 days.** Concrete, not strategic.

**Pass 3 must have depth.** 6-8 substantial capability bullets per column minimum.

**Pass 4 must have depth.** Each of the four signal types is a real paragraph, not a throwaway.

**The capstone move must be unmistakable.** THE move.

**Color discipline is absolute.** Yellow, white, black, one purple, one green. No amber, no orange, no red.

**Readability is absolute.** Body text is F5F5F5 on dark cards. Never grey-on-dark that disappears.

## Voice and Tone

Write the artifact content in a direct, confident tone. Like a coach who already sees what is coming and is telling you plainly. Clear-eyed and concrete.

Do this:
- Clear, direct, no hedging
- Specific timeframes and concrete numbers
- "You" or the specific name when addressing the participants
- Bold declarations about what is coming

Never do this:
- Never use: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets
- Never use semicolons
- Never hedge with "could potentially" or "might consider"
- Never be vague when you can be specific

## After Delivery

After presenting the artifact, offer:
1. **"Want me to turn the top pain into a standalone reference note?"** — Capture the biggest forecast as its own asset
2. **"Want me to generate content from what was found?"** — Each future pain is a LinkedIn post, podcast episode, or newsletter edition waiting to be written
3. **"Want the external client-facing version with pricing and CTA?"** — If this is being productized for a client