Discovery Sprint Planner
Plan a time-boxed discovery sprint: rank desirability, usability, feasibility, and viability risks, and test each with preset kill criteria.
Before & after
Same prompt, same agent — the only difference is the skill.
Product discovery is a structured way to validate assumptions before you build. You could talk to potential customers to understand their problems, then test whether your proposed solution actually solves them. It's helpful to document your key assumptions upfront — who the customer is, what problem they have, how big the problem is — then design conversations or experiments to test each assumption. You might do customer interviews, surveys, or even a landing page test. The goal is to get evidence that people would actually pay for your solution. What's your initial hypothesis about who your customer is and what problem you're solving?
DISCOVERY SPRINT PLAN (3 weeks) WEEK 1: ASSUMPTION MAPPING Assumption 1: ICP is technical founders, ages 28-40, building SaaS Assumption 2: Pain point is onboarding complexity (estimated cost $50K/year per company) Assumption 3: Willingness to pay: $500-2000/month Assumption 4: Main competitor is in-house solution, not point tools WEEK 2: CUSTOMER INTERVIEWS (12 interviews) → Recruit: 3 failed founders, 4 current founder/CEOs, 5 engineering leads → Question arc: Current process (15 min) → Problem depth (15 min) → Solution reaction (10 min) → Output: Transcripts + synthesis of top 3 pain points + buyer readiness score WEEK 3: LANDING PAGE TEST → Build simple one-pager describing solution (no product) → Drive 200-300 visitors via paid ads ($500 budget) → Measure: Conversion rate target 5-8% email signup → If below 3%, concept fails validation DECISION GATE Green light → Proceed to MVP: All 3 assumptions validated, 60%+ interviewees said they'd try it Red light → Pivot or abandon: High contradiction in interviews, landing page converts below 2% Yellow light → Iterate discovery: Assumption 2 strong but 1 and 3 weak, refocus interviews OUTPUT DELIVERABLES • Cleaned interview recordings (anonymized) • Assumption validation matrix (yes/no/partial per assumption) • 1-pager: top 5 findings and recommendation
About this skill
Teams often test the easy assumption (can users click through a prototype?) while the real risk is whether anyone wants it or whether the business can support it. This skill plans a short discovery sprint that tests the riskiest assumption first and ends in a clear decision.
What it does
- Frames the opportunity as a customer problem and generates several candidate solutions
- Maps desirability, usability, feasibility, and viability assumptions and ranks them by risk
- Picks the cheapest test for each: fake door, concierge, prototype, spike, or stakeholder sign-off
- Sets proceed and kill thresholds before any data comes in
- Checks an opportunity solution tree for solutions posing as opportunities
What you get
A sprint plan with the problem statement, ranked assumptions, test designs with thresholds and owners, a schedule, and a decision date.
Best for
Product managers and product trios deciding whether a feature request deserves a quarter of engineering time.
SKILL.md preview
---
name: product-discovery
description: Plan and run a time-boxed discovery sprint for a feature or opportunity inside an existing product - frame the customer problem, map desirability, usability, feasibility, and viability assumptions, rank them by risk, and design the cheapest in-product or prototype test for each with pass and kill thresholds set before the test runs. Use when the user says "we want to validate this before we build it", "plan a discovery sprint", "map our assumptions", "is our opportunity solution tree sound?", "how do we test this with our users?", "should we do a fake door test?", or "what's the riskiest assumption here?".
---
# Discovery Sprint Planner
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.