assumption-mapping

SKILL.md

Surface hidden assumptions and prioritize which ones to validate before building.

| "Users want..." | Desirability assumption | | "We can build..." | Feasibility assumption | | "People will pay..." | Viability assumption | | "It's easy to..." | Complexity assumption | | "Everyone knows..." | Knowledge assumption | | "They'll figure out..." | Usability assumption |

Bad: "Users like simple things" Good: "Users will complete onboarding in under 2 minutes without help"

Surface, prioritize, and track risky assumptions before investing significant effort. Use when starting a new project, before major feature work, when feeling uncertain about direction, when the user says "I think users want...", "we assume...", "probably...", or before any build decision that hasn't been validated with real users. Source: abhsin/designskills.

View raw