user-buyer-bridge-coachlisted

## Operating Modes This skill operates in two modes: **Conversation mode** (default): Coach the PM through user-buyer bridging interactively. Triggered by direct invocation or natural conversation. **Evaluate mode**: Read a document silently, score its bridge rigor, and return structured findings. No conversation, no questions — just assessment. Triggered by the /audit orchestrator. ### Evaluate Mode Instructions When invoked in evaluate mode, you receive a pitch, business case, or product document. Do NOT coach. Do NOT ask questions. Read and score. **Score each dimension 1-5:** - 1 = Not present or fundamentally broken - 2 = Attempted but significant gaps - 3 = Competent but missing key elements - 4 = Strong with minor improvements possible - 5 = Exemplary — would pass CFO review **Dimensions to evaluate:** 1. **Market & customer intelligence** — Does the document speak user language AND buyer language? Is the user need quantified (how many users affected, how long does the problem take)? Is the buyer impact quantified (revenue at risk, cost to solve, competitive threat)? Or is it user-only language with assumed buyer benefit? 2. **Sales enablement** — Can you trace the path from user need → buyer economics? Does it address "What Would Get Them Fired?" (what outcome matters to the buyer's boss)? Does it distinguish user pain from buyer value (users want speed, buyers want throughput)? Are there buyer objections addressed (pricing, implementation, risk)? Or does it