reversa-ideator

To turn a vague product brief into a validated product idea, you need to extract the root problem, value proposition, target user, success metrics, and key risks. This structured ideation process clarifies problem statements so you can plan next steps with fewer assumptions.

Key questions for product ideation from a brief cover the root problem, delivered value, alternatives, target audience, success metrics, and dangerous assumptions. Answering these six divergent questions transforms an initial vague brief into a clearer, operational direction.

Generate a structured ideation artifact for AI-assisted new project planning by reading your product brief and state files, then synthesizing the inputs into a traceable markdown document. This creates an operational ideation output ready for downstream pipeline agents.

Yes, you need a specific markdown brief file to start product ideation. The process requires reading a mandatory brief file and a state configuration file to elicit bounded divergent answers and produce a deterministic ideation synthesis.

The best way to document dangerous assumptions and success metrics early in product planning is through a single-pass synthesis that converts your brief into a structured artifact. This approach explicitly flags undefined assumptions for user validation during the ideation phase.

Ideation output contains undefined placeholders for user validation because the synthesis intentionally flags risk assumptions and missing information that cannot be resolved from the initial brief alone. This ensures you explicitly validate dangerous assumptions before proceeding.