reversa-ideator

To structure product ideation, convert a new project brief into six divergence answers covering root problem, delivered value, alternatives, target audience, success metrics, and dangerous assumptions. This forced structure surfaces high-risk areas for validation.

Generating a markdown ideation output requires an existing newproject-brief.md and a .reversa/state.json file. The skill reads these mandatory inputs to ensure brainstorming is grounded in your original project data.

Validating dangerous assumptions requires answering six guided ideation questions derived from your project brief. By explicitly defining the root problem and success metrics, you isolate the highest-risk assumptions needing immediate testing.

No, the ideation workflow stops with a clear instruction if the newproject-brief.md file is missing. This mandatory brief dependency prevents unsupported guessing during product brainstorming.

Overwriting an existing ideation.md triggers an overwrite confirmation guardrail. This idempotent output generation ensures your previously structured brainstorming results are not accidentally lost.

Yes, defining target audience success metrics is handled by answering the guided divergence questions. The workflow applies a specified template to write the final ideation markdown output to your designated folder.