product-discovery

Name: product-discovery
Availability: InStock
Author: Violet

Identify and validate user problems through a four-stage product discovery process.

Updated Aug 27, 2026

Search Tags:#validation #roadmap #hypotheses #product-discovery #user-interviews

Ready to run

npx skills add https://github.com/violetio/violet-ai-plugins --skill product-discovery-violetio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/violetio/violet-ai-plugins/tree/main/plugins/v-discovery/skills/product-discovery
Command: npx skills add https://github.com/violetio/violet-ai-plugins --skill product-discovery-violetio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often embark on product development without a structured discovery process, leading to misaligned scope and failed outcomes. This Skill codifies the four-stage discovery: Understand, Explore, Validate, Define, to align stakeholders and de-risk building the right solution.

Core Features & Use Cases

Discovery Process: Understand the problem, explore solutions, validate assumptions, define success.
Artifacts: Problem statements, user personas, solution options, validation results, and clear requirements.
Output: A cohesive discovery packet suitable for alignment and execution.

Quick Start

Run through the four phases in order and document outputs for each phase. Use the Discovery artifacts templates to record problem, hypotheses, and success metrics.

Frequently Asked Questions about product-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a product discovery process to validate the right problem before building?▼

Product discovery follows four phases: Understand the user problem through research, Explore potential solutions via brainstorming and prototyping, Validate assumptions with user testing and feedback, then Define clear requirements and success criteria. This structured approach aligns stakeholders and reduces the risk of building the wrong solution.

What artifacts and outputs should I create during product discovery?▼

Document problem statements, user personas, current state mappings, solution options with trade-off analysis, initial wireframes, validation results, technical feasibility assessments, and success criteria. These artifacts provide a discovery packet that drives alignment across teams and enables confident execution.

How do I use user interviews and support tickets to identify product problems?▼

Conduct user interviews to understand pain points directly, analyze support tickets to find recurring issues, and review usage data to spot gaps. These methods generate validated problem statements and user personas that inform which solutions to explore and test.

What's the best way to validate product hypotheses before full development?▼

Test hypotheses through rapid prototyping, user feedback sessions, A/B tests where applicable, and expert consultation. Validation results reveal which solutions resonate with users and meet technical feasibility, guiding the final requirements and scope definition.

How do I align stakeholders around product requirements and scope?▼

Use the discovery process to produce clear requirements, success metrics, and a defined scope document. Present validation results, trade-off analysis, and technical feasibility assessments to secure stakeholder sign-off before building.

When should I stop exploring solutions and move to building?▼

Stop when you have validated user problems, tested solution options against real user feedback, assessed technical feasibility, defined clear success criteria, and achieved stakeholder alignment. The discovery packet signals readiness to execute.