define-hypothesis
Defines a testable hypothesis with clear success metrics and a validation approach. Use when…
Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach
$ npx -y skills add product-on-purpose/pm-skills --skill tool-foundation-sprint-magic-lenses --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/tool-foundation-sprint-magic-lensesContext preview
The summary Claude sees to decide when to auto-load this skill.
Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach
name: tool-foundation-sprint-magic-lenses
description: Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and contradictions, and produce a top bet plus a backup plan. Use after Approach Options is signed. Lens scoring is a sense-making tool, not mathematical truth; arbitrary precision is a smell.
license: Apache-2.0
metadata:
classification: tool
version: "1.0.0"
updated: 2026-07-04
tool: foundation-sprint
move: magic-lenses
category: validation
frameworks:
- foundation-sprint
- click
- character-note-and-vote
timebox_minutes: 105
roles:
- facilitator
- decider
- pm
prerequisites:
- tool-foundation-sprint-approach-options
inputs:
- approach summaries
- team-specific custom lenses
outputs:
- classic lens charts (customer, pragmatic, growth, money)
- custom lens charts
- pattern review
- top bet
- backup plan
- decision rationale
author: product-on-purpose<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Day 2 afternoon of a Foundation Sprint. The team evaluates each candidate approach from multiple perspectives, surfaces contradictions, and produces a top bet plus a backup plan. The Decider names both; without an explicit backup, invalidation of the top bet sends the team back to ambiguous debate.
Family contract: [`docs/reference/skill-families/foundation-sprint-skills-contract.md`](../../docs/reference/skill-families/foundation-sprint-skills-contract.md). This skill is a member of `foundation-sprint-skills`.
A single bundled artifact with six sections:
1. **Classic lens charts**: customer, pragmatic, growth, money lenses each as a 2x2 plot or qualitative position of every approach. 2. **Custom lens charts**: at least 1 team-specific lens (defensibility, mission fit, founder excitement, learning rate, etc.). 3. **Pattern review**: consistent winners across lenses, contradictions, biggest trade-off the team is making. 4. **Top bet**: the Decider's chosen approach with rationale. 5. **Backup plan**: the runner-up approach the team falls back to if the top bet invalidates. 6. **Decision rationale**: one paragraph explaining why the top bet over the backup.
See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf example.
| Lens | What it asks | Why it matters | |---|---|---| | Customer | Which approach do target customers immediately understand and want? | If customers don't get it, nothing else matters | | Pragmatic | Which approach can the team ship at quality in [build window]? | Beautiful approaches the team can't ship are not real options | | Growth | Which approach gives the team a story strong enough to acquire users without paid channels? | Friction at the door tells you about word-of-mouth potential | | Money | Which approach has the cleanest path to a paying customer? | Strategic clarity must include the revenue path | | Custom (1+ required) | Team-specific lens that captures what would otherwise be missed | Each team has a unique constraint or opportunity worth a dedicated view |
Custom lens examples: defensibility against a specific competitor, founder excitement, mission fit, learning rate, regulatory risk, partner alignment, hiring leverage.
Facilitator restates the 4 classic lenses and confirms the 1 or more custom lenses the team prepared. If no custom lens is prepared, this skill prompts the team to generate one before proceeding (per ratified spec decision).
For each lens, plot each approach on a 2x2 of (high/low value on that lens) by (high/low feasibility for that lens). Use dot positions rather than numeric scores; arbitrary precision (3.7 vs 3.8) is a smell that the team has confused sense-making with math.
The team discusses each lens briefly before plotting. Decider does not vote in this step; the Decider supervotes at the end.
After all lenses are plotted, the team identifies:
The Decider names the top bet. The chosen approach should be:
The Decider names the backup. The backup is NOT a
68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus 6 sub-agents, workflows, 200+ output samples, guides, and CI-enforced contracts. Apache 2.0.
Repo: product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when…
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions…
Creates an opportunity solution tree connecting a desired outcome to customer opportunities…
Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against…
Creates a clear problem framing document with user impact, business context, and success…
Generates structured Given/When/Then acceptance criteria for a user story or feature slice,…