idea-refine

To turn a fuzzy idea into an MVP scope, restate the concept as a How-Might-We problem, generate and stress-test key assumptions, and define a bounded scope with a clear not-doing list before writing full specifications.

Problem framing is restating a vague concept into a structured How-Might-We statement to address user needs. You need it during early-stage ideation to prevent premature feature development and ensure you target the correct product direction before committing resources.

Identify and stress-test key assumptions by generating multiple direction options, clustering them, and challenging their underlying hypotheses. This process reveals open questions and validates whether your proposed product direction is viable before building an MVP.

No, this approach does not generate a complete product requirements document or direct engineering plans. It outputs a one-page problem statement, recommended direction, assumptions, MVP scope, not-doing list, and open questions to guide later PRD writing.

Yes, you can use MVP scoping with guardrails for early-stage ideation without a full spec. It defines a bounded MVP scope and a not-doing list to validate your idea quickly, explicitly avoiding complete specification writing or direct implementation.

The best way to frame a problem statement and define a not-doing list is to restate your idea as a How-Might-We question, stress-test core assumptions, and establish strict MVP boundaries. This yields a testable frame and clear exclusions.