suposicoes

Designs the smallest viable test to validate or invalidate critical product assumptions.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill suposicoes-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: suposicoes
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/suposicoes
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill suposicoes-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams routinely build solutions on untested assumptions, wasting effort on ideas that fail late. This Skill structures assumption testing so you identify the riskiest beliefs first and validate them with the lightest possible method before committing resources. ## Core Features & Use Cases - Assumption Mapping and Prioritization: Lists all assumptions across desirability, usability, feasibility, viability, and ethical dimensions, then ranks them on an importance-vs-evidence 2x2 matrix. - AFTER Test Selection: Chooses the lightest meaningful test from 28 techniques organized by Gilad's AFTER model (Assessment, Fact-Finding, Tests, Experiments, Release Results), from cheap internal assessments to A/B tests and staged rollouts. - Hypothesis and Prediction Discipline: Writes Lean UX hypothesis statements with measurable success criteria and forces a stated prediction before running the test, so the gap between expectation and reality becomes the learning. - Use Case: A PM believes users will switch from a competitor tool. The Skill maps that desirability assumption, flags it as high-importance/low-evidence, and recommends a concierge test with defined success criteria before any engineering begins. ## Quick Start Use the suposicoes skill to map the assumptions behind my proposed feature and design the cheapest test for the riskiest one.

Frequently Asked Questions about suposicoes

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

FAQPage Schema
How do I test a product assumption before building a feature?▼

Map all assumptions, prioritize them on an importance-versus-evidence matrix, then pick the lightest test that produces meaningful signal. Start with cheap options like surveys or data analysis before prototypes, and define measurable success criteria upfront.

What is the AFTER model for assumption testing?▼

AFTER is Gilad's framework organizing 28 test techniques into five stages: Assessment, Fact-Finding, Tests, Experiments, and Release Results. Stages are ordered by cost and confidence, so you always start with the cheapest method that answers your question.

Which assumptions should I test first in product discovery?▼

Test assumptions that are high importance and low evidence first, the top-left quadrant of the 2x2 matrix. These are the beliefs most likely to kill the solution if wrong and least supported by current data.

When should I use an A/B test versus a concierge test?▼

Use a concierge test when you need high signal quickly with manual service delivery over days. Reserve A/B tests for when you have real users at scale and need statistical comparison, since they require two or more weeks and significant traffic.

How do I write a hypothesis with measurable success criteria?▼

Use the Lean UX format: state what you will build, for whom, the expected outcome, and the measurable signal proving you are right. The fourth clause defining the observable signal is what makes the hypothesis testable.

What are the limitations of stakeholder reviews for validating assumptions?▼

Stakeholder reviews produce low-quality signal because internal expert judgment often reflects organizational mythology rather than user evidence. Treat stakeholder beliefs as unvalidated assumptions until confirmed by external data like interviews or behavioral tests.