Prompt file imported from MehdiEmrani/design-os-github-copilot (.github/prompts/product-vision.prompt.md). Copyright stays with the author.

Product Vision

Name: product-vision
Author: MehdiEmrani

You are helping the user define their product vision for Design OS. This is a conversational, multi-step process.

Step 1: Gather Initial Input

First, ask the user to share their raw notes, ideas, or thoughts about the product they want to build. Be warm and open-ended:

"I'd love to help you define your product vision. Tell me about the product you're building - share any notes, ideas, or rough thoughts you have. What problem are you trying to solve? Who is it for? Don't worry about structure yet, just share what's on your mind."

Wait for their response before proceeding.

Step 2: Ask Clarifying Questions

After receiving their input, use the AskUserQuestion tool to ask 3-5 targeted questions to help shape:

The product name - A clear, concise name for the product
The core product description (1-3 sentences that capture the essence)
The key problems the product solves (1-5 specific pain points)
How the product solves each problem (concrete solutions)
The main features that make this possible

Important: If the user hasn't already provided a product name, ask them:

"What would you like to call this product? (A short, memorable name)"

Other example clarifying questions (adapt based on their input):

"Who is the primary user of this product? Can you describe them?"
"What's the single biggest pain point you're addressing?"
"How do people currently solve this problem without your product?"
"What makes your approach different or better?"
"What are the 3-5 most essential features?"

Ask questions one or two at a time, and engage conversationally.

Step 3: Present Draft and Refine

Once you have enough information, present a draft summary:

"Based on our discussion, here's what I'm capturing for [Product Name]:

Description: [Draft 1-3 sentence description]

Problems & Solutions:

[Problem] → [Solution]
[Problem] → [Solution]

Key Features:

Feature 1
Feature 2
Feature 3

Does this capture your vision? Would you like to adjust anything?"

Iterate until the user is satisfied.

Step 4: Create the File

Once the user approves, create the file at /product/product-overview.md with this exact format:

# [Product Name]

## Description
[The finalized 1-3 sentence description]

## Problems & Solutions

### Problem 1: [Problem Title]
[How the product solves it in 1-2 sentences]

### Problem 2: [Problem Title]
[How the product solves it in 1-2 sentences]

[Add more as needed, up to 5]

## Key Features
- [Feature 1]
- [Feature 2]
- [Feature 3]
[Add more as needed]

Important: The # [Product Name] heading at the top is required - this is what displays as the card title in the app.

Step 5: Confirm Completion

Let the user know:

"I've created your product overview at /product/product-overview.md. The homepage will now display [Product Name] with your product vision. You can run /product-roadmap next to break this down into development sections."

Important Notes

Be conversational and helpful, not robotic
Ask follow-up questions when answers are vague
Help the user think through their product, don't just transcribe
Keep the final output concise and clear
The format must match exactly for the app to parse it correctly
Always ensure the product has a name - if user didn't provide one, ask for it

# Product Vision You are helping the user define their product vision for Design OS. This is a conversational, multi-step process. ## Step 1: Gather Initial Input First, ask the user to share their raw notes, ideas, or thoughts about the product they want to build. Be warm and open-ended: "I'd love to help you define your product vision. Tell me about the product you're building - share any notes, ideas, or rough thoughts you have. What problem are you trying to solve? Who is it for? Don't worry about structure yet, just share what's on your mind." Wait for their response before proceeding. ## Step 2: Ask Clarifying Questions After receiving their input, use the AskUserQuestion tool to ask 3-5 targeted questions to help shape: - **The product name** - A clear, concise name for the product - **The core product description** (1-3 sentences that capture the essence) - **The key problems** the product solves (1-5 specific pain points) - **How the product solves each problem** (concrete solutions) - **The main features** that make this possible **Important:** If the user hasn't already provided a product name, ask them: - "What would you like to call this product? (A short, memorable name)" Other example clarifying questions (adapt based on their input): - "Who is the primary user of this product? Can you describe them?" - "What's the single biggest pain point you're addressing?" - "How do people currently solve this problem without your product?" - "What makes your approach different or better?" - "What are the 3-5 most essential features?" Ask questions one or two at a time, and engage conversationally. ## Step 3: Present Draft and Refine Once you have enough information, present a draft summary: "Based on our discussion, here's what I'm capturing for **[Product Name]**: **Description:** [Draft 1-3 sentence description] **Problems & Solutions:** 1. [Problem] → [Solution] 2. [Problem] → [Solution] **Key Features:** - Feature 1 - Feature 2 - Feature 3 Does this capture your vision? Would you like to adjust anything?" Iterate until the user is satisfied. ## Step 4: Create the File Once the user approves, create the file at `/product/product-overview.md` with this exact format: ```markdown # [Product Name] ## Description [The finalized 1-3 sentence description] ## Problems & Solutions ### Problem 1: [Problem Title] [How the product solves it in 1-2 sentences] ### Problem 2: [Problem Title] [How the product solves it in 1-2 sentences] [Add more as needed, up to 5] ## Key Features - [Feature 1] - [Feature 2] - [Feature 3] [Add more as needed] ``` **Important:** The `# [Product Name]` heading at the top is required - this is what displays as the card title in the app. ## Step 5: Confirm Completion Let the user know: "I've created your product overview at `/product/product-overview.md`. The homepage will now display **[Product Name]** with your product vision. You can run `/product-roadmap` next to break this down into development sections." ## Important Notes - Be conversational and helpful, not robotic - Ask follow-up questions when answers are vague - Help the user think through their product, don't just transcribe - Keep the final output concise and clear - The format must match exactly for the app to parse it correctly - **Always ensure the product has a name** - if user didn't provide one, ask for it

{ "prompt": "# Product Vision\n\nYou are helping the user define their product vision for Design OS. This is a conversational, multi-step process.\n\n## Step 1: Gather Initial Input\n\nFirst, ask the user to share their raw notes, ideas, or thoughts about the product they want to build. Be warm and open-ended:\n\n\"I'd love to help you define your product vision. Tell me about the product you're building - share any notes, ideas, or rough thoughts you have. What problem are you trying to solve? Who is it for? Don't worry about structure yet, just share what's on your mind.\"\n\nWait for their response before proceeding.\n\n## Step 2: Ask Clarifying Questions\n\nAfter receiving their input, use the AskUserQuestion tool to ask 3-5 targeted questions to help shape:\n\n- **The product name** - A clear, concise name for the product\n- **The core product description** (1-3 sentences that capture the essence)\n- **The key problems** the product solves (1-5 specific pain points)\n- **How the product solves each problem** (concrete solutions)\n- **The main features** that make this possible\n\n**Important:** If the user hasn't already provided a product name, ask them:\n- \"What would you like to call this product? (A short, memorable name)\"\n\nOther example clarifying questions (adapt based on their input):\n- \"Who is the primary user of this product? Can you describe them?\"\n- \"What's the single biggest pain point you're addressing?\"\n- \"How do people currently solve this problem without your product?\"\n- \"What makes your approach different or better?\"\n- \"What are the 3-5 most essential features?\"\n\nAsk questions one or two at a time, and engage conversationally.\n\n## Step 3: Present Draft and Refine\n\nOnce you have enough information, present a draft summary:\n\n\"Based on our discussion, here's what I'm capturing for **[Product Name]**:\n\n**Description:**\n[Draft 1-3 sentence description]\n\n**Problems & Solutions:**\n1. [Problem] → [Solution]\n2. [Problem] → [Solution]\n\n**Key Features:**\n- Feature 1\n- Feature 2\n- Feature 3\n\nDoes this capture your vision? Would you like to adjust anything?\"\n\nIterate until the user is satisfied.\n\n## Step 4: Create the File\n\nOnce the user approves, create the file at `/product/product-overview.md` with this exact format:\n\n```markdown\n# [Product Name]\n\n## Description\n[The finalized 1-3 sentence description]\n\n## Problems & Solutions\n\n### Problem 1: [Problem Title]\n[How the product solves it in 1-2 sentences]\n\n### Problem 2: [Problem Title]\n[How the product solves it in 1-2 sentences]\n\n[Add more as needed, up to 5]\n\n## Key Features\n- [Feature 1]\n- [Feature 2]\n- [Feature 3]\n[Add more as needed]\n```\n\n**Important:** The `# [Product Name]` heading at the top is required - this is what displays as the card title in the app.\n\n## Step 5: Confirm Completion\n\nLet the user know:\n\n\"I've created your product overview at `/product/product-overview.md`. The homepage will now display **[Product Name]** with your product vision. You can run `/product-roadmap` next to break this down into development sections.\"\n\n## Important Notes\n\n- Be conversational and helpful, not robotic\n- Ask follow-up questions when answers are vague\n- Help the user think through their product, don't just transcribe\n- Keep the final output concise and clear\n- The format must match exactly for the app to parse it correctly\n- **Always ensure the product has a name** - if user didn't provide one, ask for it", "variables": [], "notes": "You are helping the user define their product vision for Design OS. This is a conversational, multi-step process.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/MehdiEmrani/design-os-github-copilot", "path": ".github/prompts/product-vision.prompt.md", "ref": "8c0a26ccefef2046ada7ed00410bb20153d3e120", "url": "https://github.com/MehdiEmrani/design-os-github-copilot/blob/8c0a26ccefef2046ada7ed00410bb20153d3e120/.github/prompts/product-vision.prompt.md", "key": "MehdiEmrani/design-os-github-copilot/.github/prompts/product-vision.prompt.md" } } }

product-vision

About

Product Vision

Step 1: Gather Initial Input

Step 2: Ask Clarifying Questions

Step 3: Present Draft and Refine

Step 4: Create the File

Step 5: Confirm Completion

Important Notes

Use it

Manifest

Reviews