Menu
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
Create structured visualizations of stakeholder perspectives (says, thinks, does, feels) to build deep understanding. Use when conducting user research or validating assumptions.
Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue.
Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research.
Distinguish user wants from underlying needs to guide solution design. Use when stakeholders make feature requests or during Define phase.
Create clear leadership presentations that communicate findings and enable good decisions. Use at end of each phase or before major commitments.
| name | assumption-validation |
| description | Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk. |
Test whether an assumption is true or false before making commitments based on it.
Make it testable. Transform vague beliefs into specific claims:
Be explicit about criteria:
Match method to assumption type:
User behavior/needs: Interviews, observation, surveys Technical feasibility: Spikes, prototypes, vendor demos Market conditions: Market research, competitor analysis Business viability: Financial modeling, expert consultation
Conduct research with focus on disproving, not confirming:
Record findings in currentstate.json:
If validated: Proceed with confidence, but stay alert for new evidence
If invalidated:
If partially validated:
Assumption: "Field technicians need offline access"
Validation Plan:
Findings:
Result: VALIDATED — Offline access is a critical requirement
Action: Prioritize offline functionality in ideation phase
