# How to Run the /discover Command for Full Product Discovery > Learn to run the /discover command in phuryn/pm-skills for comprehensive product discovery. This slash command generates a full discovery plan document by combining key product development skills. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: how-to-guide - Published: 2026-06-09 --- **The `/discover` command in the `phuryn/pm-skills` repository chains brainstorm, assumption-mapping, prioritization, and experiment-design skills into a single slash-command invocation that produces a complete discovery-plan document.** Invoking `/discover` inside the **pm-product-discovery** plugin triggers an end-to-end product-discovery workflow that adapts to both live products and new concepts. As implemented in the source code, the command is defined in [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md) and documented across the plugin’s README and root README. Whether you are validating a fresh idea or refining an existing feature set, learning how to run the `/discover` command for full product discovery gives you a structured, repeatable process for de-risking product decisions. ## What the /discover Command Does The `/discover` command is the centerpiece of the **pm-product-discovery** plugin. It orchestrates a complete product-discovery workflow by chaining specialized skills into a single end-to-end process. ### The Four-Stage Workflow When you invoke `/discover `, the system performs these stages: 1. **Brainstorm ideas** — generates feature concepts from the perspectives of product, design, and engineering. 2. **Identify assumptions** — surfaces the underlying hypotheses that must be true for the ideas to deliver value. 3. **Prioritize assumptions** — ranks the riskiest assumptions using an **importance × (1 − satisfaction)** score, also known as the **Opportunity Score**. 4. **Design experiments** — proposes concrete validation steps such as user interviews, prototypes, or A/B tests. ### Context-Aware Adaptation According to the source files, the command adapts to two product contexts: - **Existing product** — continuous discovery on a live product with real users. - **New product** — initial discovery for a concept that has not yet been validated. ## How to Run the /discover Command for Product Discovery You invoke the command via a slash (`/`) prefix, just like any other Claude PM workflow. ### Full Discovery for a New Product Use a concise description of your concept as the argument: ```markdown /discover AI-powered meeting summarizer for remote teams ``` ### Full Discovery for an Existing Product For live products, describe the feature or improvement you want to explore: ```markdown /discover Smart notification system for our project-management tool ``` ### Interactive Mode If you run `/discover` without an argument, the assistant prompts you for the target idea and asks follow-up questions such as, "What decisions will this discovery inform?" to keep the conversation focused: ```text /discover > What product or concept would you like to discover? ``` ## The Discovery-Plan Output After the workflow finishes, the output is a **discovery-plan document** that captures the brainstormed ideas, mapped assumptions, prioritized risks, and experiment designs. This document is intended to be a living artifact that you can iteratively update as you run experiments. You can export it, share it with stakeholders, or feed it into later stages such as strategy or execution. ## Key Source Files in phuryn/pm-skills The following files define and document the command: - [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md) — Definition of the `/discover` command, its workflow stages, and example invocations. - [`pm-product-discovery/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/README.md) — Overview of the discovery plugin and its skills, plus context for how `/discover` fits into the broader ecosystem. - [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) (lines 16–42) — High-level introduction to the command and its place among other slash commands in the repository. ## Summary - The `/discover` command orchestrates a full product-discovery workflow across four stages: brainstorm, assumption identification, prioritization via **Opportunity Score**, and experiment design. - It adapts automatically to **existing products** undergoing continuous discovery or **new products** seeking initial validation. - You invoke it with `/discover `, or run `/discover` alone to receive an interactive prompt and focused follow-up questions. - The final output is a shareable **discovery-plan document** defined in [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md). ## Frequently Asked Questions ### What happens if I run `/discover` without providing a product idea? If you invoke `/discover` with no argument, the assistant automatically prompts you with the question, "What product or concept would you like to discover?" It may also ask follow-ups like, "What decisions will this discovery inform?" to keep the session focused and ensure the workflow has a clear starting point. ### How does the `/discover` command prioritize assumptions? The command ranks assumptions using an **Opportunity Score** calculated as importance multiplied by (1 minus satisfaction). This surfaces the riskiest hypotheses so you can address the highest-impact unknowns first. ### Can I use `/discover` for a product that is already live? Yes. The command detects context and switches to a continuous-discovery mode for existing products with real users, rather than the initial-validation mode used for brand-new concepts. ### Where is the `/discover` command defined in the pm-skills repository? The command definition, workflow description, and usage examples live in [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md). Broader plugin context appears in [`pm-product-discovery/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/README.md), and the root [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) (lines 16–42) positions it among the other slash commands.