sm:invalidate-prep

To validate assumptions before coding, you can surface and rank the hidden bets underlying your concept by cost-if-wrong, then generate named personas and testable problem statements to guide invalidation interviews.

Ranking assumptions by risk during concept validation involves evaluating each assumption's cost-if-wrong to identify your riskiest bets, ensuring you prioritize invalidation interviews for the most critical product unknowns.

Preparing for invalidation interviews requires generating explicit persona definitions and testable problem statements from your core concept, providing ready-to-run interview prompts to structure your validation workflow.

Yes, you can excavate load-bearing assumptions directly from a product spec to generate testable problem statements, enabling early-stage validation and accelerating the workflow before feature development begins.

Assumption invalidation works for early-stage concept validation without prior dependencies, directly processing your raw concept to surface gaps, name personas, and output a reproducible structure for immediate interviews.

You should not use assumption invalidation if your concept is already validated and code is written, as this process targets pre-code excavation of hidden risks, persona generation, and interview preparation.