Product Discovery logo

Product Discovery

Community
MartinOlivero
product-discovery

This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to start. Trigger phrases include "I have an idea for a product", "not sure what to build", "what should the MVP be", "where do I start", "is this idea any good", "help me scope this", "I want to build something but". Inspired by Design Sprint and Lean Startup. It separates the problem from the solution, validates the market, and defines a prioritized MVP.

Overview

PublisherMartinOlivero
Repositorysaas-builder
Skill nameproduct-discovery
Stars
4
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by MartinOlivero on GitHub. Read the source before you install it.

Installation

Install the Product Discovery AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/MartinOlivero/saas-builder/tree/main/skills/product-discovery
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/MartinOlivero/saas-builder.git /tmp/saas-builder
mkdir -p .claude/skills
cp -r /tmp/saas-builder/skills/product-discovery .claude/skills/product-discovery
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Product Discovery in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Product Discovery on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Product Discovery is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Product Discovery

This skill turns a fuzzy idea into a sharp, buildable MVP. It is inspired by Design Sprint and Lean Startup, and it resists the urge to jump to features before the problem is understood.

Analogy: do not prescribe medicine before diagnosing the illness. Most failed products are perfectly built cures for a disease nobody has.

Workflow

PHASE 1 — Understand the problem (not the solution)

Force the conversation onto the problem first. Ask:

  • What specific problem are you solving?
  • Who has that problem? Describe that person concretely.
  • How do they solve it today? (even if it is Excel, WhatsApp, or by hand)
  • Why is that current solution not good enough?

Do not let the discussion drift to features yet. If the user describes a solution, redirect to the problem it serves.

PHASE 2 — Validate the market

  • Do you (or your target users) already pay for something similar? How much?
  • Do you know other people with this same problem?
  • Do you have access to potential customers to validate with?

The goal is evidence that the problem is real and painful enough that someone will pay.

PHASE 3 — Define the MVP

  • What is the minimum result that would make someone pay?
  • Which features are "nice to have" but not essential?
  • How soon do you want something to show?

The MVP is the smallest thing that delivers the core result — not a small version of the full vision.

PHASE 4 — Output

Deliver these five items:

  1. Problem definition — in one sentence.
  2. Ideal customer avatar — who they are, concretely.
  3. MVP scope — a prioritized feature list:
    • P0 — must exist for the MVP to deliver its core result.
    • P1 — important, but can wait for v1.1.
    • P2 — nice to have; explicitly deferred.
  4. Success metric — how we will know it worked (e.g. "10 paying users in 30 days," "40% of signups complete the core action").
  5. Concrete next step — the single next action to take.

Handoff

Once the MVP is defined, hand off to architecture-primer to decide how to build it, then ui-design to build the interface. Discovery answers (scale expectations, user type, timeline) feed directly into the architecture discovery phase — pass them along.

Frequently asked questions

What does the Product Discovery AI skill do?

This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to start. Trigger phrases include "I have an idea for a product", "not sure what to build", "what should the MVP be", "where do I start", "is this idea any good", "help me scope this", "I want to build something but". Inspired by Design Sprint and Lean Startup. It separates the problem from the solution, validates the market, and defines a prioritized MVP.

Why use Product Discovery on TypingMind?

Because you install it once and use it with any model. Product Discovery is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Product Discovery in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MartinOlivero/saas-builder/tree/main/skills/product-discovery. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Product Discovery?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Product Discovery?

As many as you like. As long as a model supports skills, you can use Product Discovery with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Product Discovery AI skill free?

Yes. It is published on GitHub by MartinOlivero under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇