Skip to main content

Overview

Collaborate with AI to brainstorm solution ideas for an opportunity—starting with your own ideas, then expanding with AI suggestions, and capturing everything in Vistaly. This works because Vistaly structures your product work as a connected graph. AI can walk through that graph to understand the strategic context before helping you ideate, making its suggestions more relevant and grounded.

Prerequisites

  • Vistaly MCP integration configured (setup guide)
  • An opportunity (or other card) you want to ideate on
  • Optional: Insights linked to the opportunity for additional context

The Prompt

Copy and paste this prompt to start the workflow:
<Goal>
Run a collaborative ideation session using the Vistaly MCP service.
</Goal>

<Context>
## Workflow Purpose
Guide the user through a collaborative ideation session—from understanding the opportunity context to generating and capturing solution ideas.

## Key Definitions
- **Opportunities**: Customer pain-points, needs, or desires. They represent gaps that can be addressed by a product team.
- **Solutions**: Ideas or features that could address an opportunity.
- **Insights**: Evidence from customer research that supports or informs opportunities.

## Role Definitions
- **facilitator**: Ask the user questions, guide the process, and wait for responses.
- **actor**: Perform an action (fetching data, making updates, processing information).
- **collaborator**: Work together with the user through back-and-forth dialogue.

## Terminal Environment
When evaluating the output formats, links should be formatted as markdown when working in a non-terminal based environment. But when working in the terminal (ex: Claude Code), you must print the name of Card or insight, followed by the full URL.
</Context>

<Steps>
<Step number="1" title="Get Starting Card" role="facilitator">
Ask the user for a Vistaly card to run the ideation session on. They can provide:
- A Card ID (e.g., `card_abc123`)
- A Vistaly URL
- The card name or rough text to search for

**Note**: While this workflow works best with an opportunity card, you can start from any card type. If they provide something other than an opportunity, proceed anyway.
</Step>

<Step number="2" title="Locate the Card" role="actor">
Using the Vistaly MCP server, locate the card with the input provided in step 1.

If multiple cards match, present the options for the user to choose from.
</Step>

<Step number="3" title="Get Context" role="actor">
Fetch the story context using `getCardContext`:

1. **Ancestors**: Call `getCardContext` with:
   - Direction: `ancestors`
   - Include insights: `true`
   - Include target card: `true`

2. **Descendants**: Call `getCardContext` with:
   - Direction: `descendants`
   - Max levels: `2`
   - Include insights: `false`
   - Include target card: `false`

Build a mental map of where this card sits in the hierarchy and what context surrounds it.
</Step>

<Step number="4" title="Display the Story" role="actor">
Present the story context using OUTPUT_FORMAT step="4".

Show the hierarchy from highest ancestor down to the target card, giving the user a clear picture of the strategic context before ideating.
</Step>

<Step number="5" title="Collect User Solutions" role="facilitator">
Ask the user to share any solution ideas they've already been thinking about.

**Important**: Collect their ideas BEFORE you generate any of your own. This ensures their thinking isn't anchored by AI suggestions.
</Step>

<Step number="6" title="Collaborative Solution Development" role="collaborator">
Generate 5 distinct solutions (different from the user's) that could address the opportunity.

Present both lists and engage in back-and-forth discussion to refine these solutions at a high-level before continuing. Don't feel you always need to agree with the user.

**IMPORTANT**: Make sure the solutions are unique and not simple variations of one another.

**NOTE**: If you need more context about specific product details:
- If running in Claude Code, read relevant parts of the codebase
- Use the Vistaly MCP documentation to learn about the existing product
</Step>

<Step number="7" title="Add Solutions to Vistaly" role="actor">
1. Once you've agreed on a final set of solutions, display the ID of the target card with a link for verification
2. Ask the user to confirm before adding
3. Add all agreed solutions as children of the target card using the Vistaly MCP server

**IMPORTANT**: This must be the same card located in step 2.
</Step>

<Step number="8" title="Export Session Summary" role="actor">
Generate a summary of the ideation session using OUTPUT_FORMAT step="8".

This should be copyable markdown that can be shared in Slack, docs, or other tools.
</Step>
</Steps>

<Output_Formats>
<Output_Format step="4">
**Progress**: Step 4 of 8 - Story Context

## Story Context

## {Card Type}: {Tag}
Labels: {Label(s)}
{Card Name}

## {Card Type}: {Tag}
Labels: {Label(s)}
{Card Name}

[...continue for all ancestor cards...]

## **{Target Card Type}**
**Labels: {Label(s)}**
**{Card Name}**

**Notes:**
- Don't print metric values
- {Tag} is reserved for opportunities: "Top-level" for topmost, "Child" for others
- Labels line only displays if labels exist
- Add space between each card
- Start with highest ancestor, end with target card
- Bold the target card's body text
- Don't print any other explanatory text
</Output_Format>

<Output_Format step="6">
**Progress**: Step 6 of 8 - Solution Development

## Solutions

**Your Solutions:**

1. [Solution name] - [brief description]
2. [Solution name] - [brief description]

**My Generated Solutions:**

[continuing numbering from your list]
3. [Solution name] - [brief description]
4. [Solution name] - [brief description]
5. [Solution name] - [brief description]
6. [Solution name] - [brief description]
7. [Solution name] - [brief description]

Which solutions should we refine or move forward with?
</Output_Format>

<Output_Format step="7">
**Progress**: Step 7 of 8 - Adding Solutions to Vistaly

## Solutions Ready for Vistaly

**Target Card**: [{card_name}]({vistaly_card_url}) (ID: {card_id})

**Solutions to Add:**

1. [Solution name] - [brief description]
2. [Solution name] - [brief description]
[...]

Should I add these {X} solutions to the card above?
</Output_Format>

<Output_Format step="8">
## Ideation Session Summary

**Date**: {Today's Date}
**Target**: [{Card Name}]({vistaly_card_url})

### Context

{1-2 sentence summary of the opportunity/card and its strategic context from ancestors}

### Solutions Generated

**{X} solutions were identified and added to Vistaly:**

1. **{Solution Name}** - {brief description}
2. **{Solution Name}** - {brief description}
[...]

### Next Steps

- Review solutions in Vistaly and add any additional details
- Consider running a solution deep dive on promising solutions
- Prioritize which solutions to explore further

---
*Generated via Vistaly ideation session*
</Output_Format>
</Output_Formats>

Tips for Success

Start with Your Ideas First

Always share your own solution ideas before asking for AI suggestions. This prevents anchoring bias and ensures your original thinking is captured.

Use an Opportunity Card

While you can start from any card, opportunities work best. They have the right context (parent outcomes, linked insights) to generate relevant solutions.

Push Back on AI Suggestions

The collaborative step is meant to be a discussion. Challenge suggestions that don’t fit, ask for variations, or combine ideas. You’re in control.

Share the Summary

The final summary is designed to be shareable. Copy it into Slack or your team docs to keep stakeholders informed about ideation progress.

When to Use This Recipe

  • Starting discovery on an opportunity - Generate initial solution candidates to explore
  • Expanding your solution space - Break out of tunnel vision with fresh AI perspectives
  • Team brainstorming sessions - Use as a structured facilitation guide with your team
  • Capturing ad-hoc ideas - Turn scattered thoughts into structured solutions in Vistaly