About hypothesis-builder
hypothesis-builder is a skill for growth and sales teams that turns an ICP, buyer personas, signals, and available angles into a prioritized campaign-testing matrix. It filters incoherent combinations and groups near-duplicates so the result serves as a testing backlog.
Key features
- 01Combines personas, signals, and angles
- 02Filters incoherent combinations
- 03Groups similar hypotheses
- 04Scores and sorts by priority
- 05Produces one-line descriptions
Use cases
- 01Planning tests for an ICP or vertical
- 02Prioritizing outreach hypotheses
- 03Expanding a campaign backlog
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ victor-shulga/ outbound-engine-skills --skill hypothesis-builderAfter installing, type/hypothesis-builderin Claude Code to confirm it loaded.
Details
From the project READMEHypothesis Builder
Take an ICP, a set of buyer personas, and a list of signals — generate a full testing matrix of campaign hypotheses to run.
What you need
- ICP definition (industry, company size, geography)
- Target personas (2–5 roles you want to reach)
- Buyer signals available (hiring, funding, tool change, leadership change, etc.)
- Angles available (problem-based, time-based, social proof, competitive, etc.)
Process
- Map every combination of: persona × signal × angle
- Remove combinations that are logically incoherent (e.g., "new CRO" signal sent to an SDR)
- Group into clusters by similarity — don't list near-duplicates as separate hypotheses
- Assign a priority score to each hypothesis (1–3) based on: signal specificity, persona authority, angle strength
- Return the full matrix sorted by priority, with a one-line description of each
Output format
Hypothesis matrix: [ICP name]
Generated: [date]
Total hypotheses: [n]
PRIORITY 1 — Highest expected performance
H01 | [Persona] | [Signal] | [Angle] | [One-line description]
H02 | ...
PRIORITY 2 — Worth testing
H03 | ...
PRIORITY 3 — Low conviction, test last
H08 | ...
Recommended starting set: [H01, H02, H04] — run these first
Notes
- Aim for 20–50 hypotheses for a single ICP/vertical — too few means under-testing, too many means you lack focus
- Priority 1 hypotheses should have a specific, recent signal + a senior decision-maker persona
- If signals list is vague, ask for specific examples before generating
- The matrix is not a campaign list — it's a backlog. Only run what you can actually resource
Comments
Markdown supported