reversa-ideator

Structured product ideation transforms a raw brief by guiding you sequentially through the root problem, delivered value, alternatives, target audience, success metrics, and risky assumptions to produce a validated markdown synthesis.

Assumption testing in product discovery identifies and records risky assumptions and vague answers during brainstorming, ensuring teams align early by validating dangerous hypotheses before committing to development.

To start structured brainstorming, provide an initial brief to the agent and invoke the ideation command, which reads the brief file and elicits one question at a time to map the core product direction.

Success metrics defined during product concept shaping should directly measure the delivered value and target audience alignment identified in the ideation plan, ensuring the product direction is quantifiable from the start.

Generating ideation output requires a mandatory initial brief file; the process applies guardrails for missing briefs and explicitly records undefined or vague answers for follow-up instead of hallucinating data.

Asking for alternatives during structured ideation forces divergent thinking, ensuring the team evaluates multiple approaches to the root problem before converging on a single product direction in the final markdown plan.