tool-foundation-sprint-founding-hypothesis

Generates the canonical Founding Hypothesis sentence and assumption scorecard closing a Foundation Sprint.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-foundation-sprint-founding-hypothesis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-foundation-sprint-founding-hypothesis
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-foundation-sprint-founding-hypothesis
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-foundation-sprint-founding-hypothesis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams finishing a Foundation Sprint often end with scattered outputs and no single testable statement of strategy. This Skill compresses the sprint's full strategic frame into one canonical Founding Hypothesis sentence plus an assumption scorecard, so the sprint closes with a ratified, falsifiable artifact instead of vague alignment.

Core Features & Use Cases

  • Strict canonical template: Enforces the five-slot hypothesis sentence (target customer, important problem, approach, alternatives, differentiators) and rejects paraphrase or vague slots.
  • Assumption scorecard: Decomposes the hypothesis into 5-7 assumptions, each scored on current confidence with a best next test, and identifies the highest-risk assumption.
  • Calibration and ratification: Produces "why we believe" and "what could prove us wrong" lists, a recommended next validation step with owner and timeline, and a Decider sign-off checkpoint.
  • Use Case: At the end of Day 2 of a Foundation Sprint, after Magic Lenses has named a top bet, the facilitator uses this Skill in a 45-minute session to draft the hypothesis, build the scorecard, and have the Decider ratify the sprint's closing artifact.

Quick Start

Run the Foundation Sprint Founding Hypothesis skill to turn our Magic Lenses top bet and prior sprint outputs into a ratified hypothesis sentence and assumption scorecard.

Frequently Asked Questions about tool-foundation-sprint-founding-hypothesis

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

FAQPage Schema
How do I write a Founding Hypothesis for a Foundation Sprint?

Fill the strict five-slot template: target customer, important problem, approach, competitors or alternatives, and differentiators, each sourced from prior sprint outputs. The skill rejects vague slots or paraphrased structures, then the Decider ratifies the sentence verbatim.

What is an assumption scorecard in a Foundation Sprint?

An assumption scorecard decomposes the hypothesis into 5-7 assumptions, each with why it matters, a current confidence rating, and a best next test. The lowest-confidence, highest-blast-radius assumption becomes the priority for the next validation step.

When should I run the Founding Hypothesis move?

Run it at the end of Day 2 of a Foundation Sprint, after Magic Lenses is signed and a top bet and backup are named. It requires the Basics and Differentiation bundled artifacts as inputs and takes about 45 minutes.

Can I paraphrase or modify the Founding Hypothesis template?

No. The template is strict and paraphrase is rejected, including compressing slots or reordering the sentence. The strictness forces the team to fill every slot specifically rather than settling for vague wording.

What happens if the team cannot ratify the hypothesis by end of Day 2?

The sprint output is considered incomplete. The skill explicitly warns against polishing later or ratifying a vague hypothesis, since both re-litigate the strategy and undermine the sprint's purpose.