🌳

Turn discovery findings into options

Map validated findings into an opportunity-solution tree — and flag which solutions are still untested assumptions.

The value here is structure plus honesty: grouping findings into opportunities, proposing solutions, and being explicit about what's still a guess. A capable reasoning model keeps the tree coherent; the key is asking it to separate evidence from assumption.

Gemini

Gemini 3.1 Pro

Why this variant: A stable, capable reasoner — a dependable choice when you want a repeatable discovery workflow rather than the newest model. Handles the tree structure cleanly.

Prompt for Gemini 3.1 Pro

Here are our validated discovery findings:
{paste findings}
Map these into an opportunity-solution tree: the top 3 opportunities, and
2–3 candidate solutions under each. Clearly flag which solutions are
assumptions we have NOT yet tested. Use indented bullets.

Claude

Claude Opus 5

Why this variant: Best when the findings are ambiguous and you need careful reasoning about what the evidence actually supports. Tags keep findings and task distinct.

Prompt for Claude Opus 5

<findings>
{paste discovery findings}
</findings>
<task>
Build an opportunity-solution tree. For each opportunity, rate how strong
the evidence is (strong / mixed / thin) and say what would make it
stronger. Mark every solution that rests on an untested assumption with
[ASSUMPTION].
</task>