stakeholder-discovery

Map and validate offer pillar hypotheses through stakeholder interviews and pain quantification.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/alexwox/genesis-template --skill stakeholder-discovery-alexwox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-discovery
Source: https://github.com/alexwox/genesis-template/tree/main/.cursor/skills/stakeholder-discovery
Command: npx skills add https://github.com/alexwox/genesis-template --skill stakeholder-discovery-alexwox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This playbook helps teams validate an offer pillar hypothesis by finding, recruiting, and interviewing the people closest to the pain so decisions are based on quantified signals rather than assumptions. It replaces scattershot outreach and anecdotal feedback with a repeatable discovery pipeline that produces a pain proximity map, target list, outreach plan, interview protocol, and a decision-ready synthesis.

Core Features & Use Cases

  • Pain Proximity Mapping: Identify roles with the highest insight density and prioritize high-value interview targets.
  • Target List & Outreach Plan: Build a 30–50 person target list across LinkedIn, conferences, vendor ecosystems, and consultants with channel-specific expected response rates and message templates.
  • Interview Protocol & Extraction Templates: Standardized opening questions, probe sequences, post-interview extraction fields, and rules for rejecting low-quality signals.
  • Signal Detection & Synthesis: Rules for identifying pillar-validating and pillar-killing signals, saturation rules, pattern analysis tables, and validation thresholds with explicit quality gates and a 3-interview stop rule.
  • Use Case: Early-stage product teams, founders, or PMs who need to validate problem hypotheses, refine positioning, or determine willingness-to-pay before building.

Quick Start

Run stakeholder-discovery on the hypothesis "Product analytics teams at mid-market SaaS waste >8 hours weekly reconciling event data" to generate a pain proximity map, a 30-person outreach list, message templates, a 20-minute interview protocol, and a synthesis plan.

Frequently Asked Questions about stakeholder-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a product hypothesis through stakeholder interviews?

To validate a product hypothesis through stakeholder interviews, you map pain proximity, build a 30-50 person outreach list, conduct standardized interviews, and synthesize extracted signals against saturation rules and validation thresholds to make a decision.

What is a pain proximity map for customer discovery?

A pain proximity map for customer discovery identifies organizational roles with the highest insight density, allowing you to prioritize high-value interview targets who are closest to the actual problem before conducting outreach.

How many stakeholder interviews do I need to validate a problem hypothesis?

You need to meet signal saturation rules and validation thresholds to validate a problem hypothesis, which includes a 3-interview stop rule for detecting pillar-killing signals early and rejecting low-quality feedback.

What's the best way to build an outreach list for early-stage product research?

The best way to build an outreach list for early-stage product research is to target 30-50 people across LinkedIn, conferences, vendor ecosystems, and consultants, applying channel-specific expected response rates and tailored message templates.

Can I use this discovery workflow to determine willingness-to-pay before building?

Yes, you can use this discovery workflow to determine willingness-to-pay before building by applying the interview protocol and extraction templates to surface and quantify customer pain, yielding a decision-ready synthesis for go-to-market validation.

How do I identify pillar-killing signals during customer discovery?

You identify pillar-killing signals during customer discovery by applying standardized extraction rules and pattern analysis tables to interview transcripts, detecting disqualifying feedback that fails to meet explicit quality gates.