discovery_skill

This skill helps you master user discovery and research by guiding interviews, persona creation, and journey mapping to inform product decisions.
  • Python

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill pluginagentmarketplace/custom-plugin-product-manager --skill discovery

  • SKILL.md7.8 KB

Overview

This skill helps you master user discovery and research practices to validate problems before building. It teaches interview structure and techniques, synthesis methods like affinity mapping and persona creation, and journey mapping to uncover opportunities. Use it to turn customer conversations into clear product decisions and prioritized insights.

How this skill works

It guides you through recruiting and running 30–60 minute customer interviews, including scripts and time-boxed sections (opening, context, deep dive, impact, exploration, closing). After interviews it shows how to synthesize notes via affinity mapping, derive personas from evidence, map current-state customer journeys, and extract five key metrics to prioritize work. It also prescribes mixed-method sequencing (qualitative first, surveys to validate) and troubleshooting steps to recover from low participation or bias.

When to use it

  • At product discovery to validate problem/solution fit
  • Before writing requirements or roadmaps
  • When building user personas and targeting segments
  • To prioritize product opportunities based on customer impact
  • When onboarding research practices across a team

Best practices

  • Run 20–25 interviews across power users, light users, and non-users
  • Follow the 30–60 minute interview structure and ask Why five times for root causes
  • Listen 70% / talk 30% and avoid leading questions
  • Record (with consent), take timestamped notes, and debrief within 24 hours
  • Synthesize with affinity mapping and rank themes by frequency and impact

Example use cases

  • Validate the #1 problem and whether users will pay before building an MVP
  • Create 1–2 page personas with quotes, goals, pains, and decision journeys for stakeholders
  • Map current-state customer journeys to identify friction in onboarding or support
  • Run mixed-method research: exploratory interviews then a 100+ person survey to scale findings
  • Diagnose low research participation and fix recruitment or incentives quickly

FAQ

Aim for 15–25 for deep qualitative insight and at least 20–25 when possible to capture variability across segments.

What comes first: interviews or surveys?

Start with interviews to uncover the why, then run a larger survey to validate themes and estimate reach and magnitude.

How do I avoid bias during interviews?

Use neutral, open questions, let silence prompt elaboration, ask Why repeatedly, and have a second reviewer for transcripts during synthesis.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
discovery skill by pluginagentmarketplace/custom-plugin-product-manager | VeilStrat