Who is this skill for and what problem does it solve?

This skill is designed for Product Managers who don't have dedicated research support, automating the process of framing problems, building bias-free interview guides, and synthesizing raw notes into actionable evidence.

Which AI agents and note-taking tools are compatible with this skill?

The skill is compatible with AI agents that support markdown processing and can ingest text from meeting tools like Granola or Fireflies, as well as manually pasted interview notes.

What exactly is included when I acquire this skill?

You will receive a set of four distinct discovery modes—Start, Interview, Synthesize, and Package—each designed to produce a professional markdown document for your workflow.

How does the skill handle the synthesis of raw interview data?

The Synthesize mode analyzes your raw interview notes to identify recurring themes, calculate frequency counts, and generate a visual opportunity tree to validate or pivot your initial hypothesis.

How does the skill ensure that my user interviews stay objective and bias-free?

The 'Interview' mode specifically follows 'The Mom Test' methodology, ensuring questions focus on past user behavior rather than hypothetical future opinions to avoid biased or misleading feedback.

How do I handle updates or technical issues with the skill?

This skill is provided under the MIT license and is part of the pm-pilot toolkit; you can check the official GitHub repository for the latest updates and version history.

Product Discovery for PMs Without a Researcher

Example session with this skill installed

We're losing about 35% of teams in the first 90 days, mostly mid-market teams of 20 to 50 people. Usage drops off a cliff around week 6 to 8 and support tickets spike around Jira import and Slack notifications. I've run 7 interviews. Synthesize my research.

Read your context and instructions
Compiled the product discovery

Theme 1: "The Slack Gap" (6/7 interviewees)
Intensity: Hair-on-fire

Teams live in Slack. When task updates don't flow into Slack, team members stop checking [our tool]. They revert to Slack threads for status updates, which defeats the purpose.

"If it's not in Slack, it doesn't exist for my team." -- P3, Engineering Lead "I was copying and pasting updates from [tool] into Slack three times a day. I gave up at week 5." -- P1, Project Lead (churned)

Theme 2: "Champion Burnout" (5/7 interviewees)
Intensity: High

The person who brings the tool in becomes the unpaid admin. They spend 2-4 hours/week maintaining it for the team. When they burn out, nobody picks up the slack.

"I became the Jira guy. Sorry, the [your tool] guy. Nobody else knew how to set up a board." -- P5, PM (churned)

Theme 3: "The Week 3 Wall" (4/7 interviewees)
Intensity: Medium

Initial setup is smooth. But when teams try to customize workflows (week 2-3), they hit complexity. The retained teams pushed through. The churned teams didn't.

"Setting up was easy. Making it work the way WE work took forever." -- P2, Ops Lead

Opportunity Tree
Day-90 Team Retention | +-- Opportunity 1: Teams need task updates flowing into Slack without manual effort | Evidence: 6/7 interviewees. Two strongest quotes from P1, P3. | +-- Opportunity 2: Champions need the tool to reduce their admin burden, not increase it | Evidence: 5/7 interviewees. Champion burnout is a churn predictor. | +-- Opportunity 3: Teams need guided workflow customization in weeks 2-3 | Evidence: 4/7 interviewees. Retained teams got past this; churned didn't.

Hypothesis Check
Original hypothesis: Integration gaps (Jira, Slack, GitHub) cause reversion. After research: PARTIALLY CONFIRMED. Slack is critical (6/7). But Jira/GitHub are secondary. The real issue is broader: the tool doesn't embed into the team's communication layer (Slack) AND creates admin burden for the champion. Integrations are necessary but not sufficient.

Connects securely to your tools. The creator never sees your data.

About this skill

Most PMs run discovery alone. This skill walks you through a full cycle in four modes, each one producing a markdown file you can share. **Start:** dump your messy thinking. It reflects back the core problem, who is affected and your hypothesis, then writes a one-page brief. Interview: builds a Mom Test interview guide. The questions ask about past behavior, never opinions about the future. Synthesize: turns interview notes into themes with counts and quotes, an opportunity tree, and a check against your original hypothesis. Package: writes a stakeholder one-pager that leads with the evidence. Works with Granola, Fireflies or pasted notes. No UX researcher needed. Source and full pm-pilot toolkit (free, MIT): https://github.com/mshadmanrahman/pm-pilot/tree/main/plugins/pm-discovery/skills/product-discovery

How to install

Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

~30 seconds

1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.

Skills folder by agent

Click the path to copy it. Create the folder if it does not exist yet.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

Fresh listing

Recently published to Agensi

Free forever

No account required to browse

Product Discovery for PMs Without a Researcher