Files
pm-skills/pm-product-discovery
Claude 18468a95b4 Release v2.1.0: Opus 4.8-tuned pm-ai-shipping audits + CHANGELOG-driven release automation
pm-ai-shipping: mandatory Evidence citations verified before reporting,
concrete subagent fan-out contract, read-only allowed-tools on both audits,
N+1/waterfall detection and a refute pass in the performance audit,
untrusted-input hardening across the kit, parallel audits in /ship-check,
severity anchors + report consolidation, repo-relative paths.

Repo: CHANGELOG.md as release source of truth with auto-tag-and-release on
merge to main (adapted from phuryn/claude-usage, minus the .vsix build),
Tests workflow on every PR/push, unit + docs-consistency test suite,
contributor-credit conventions in CONTRIBUTING, all manifests synced at 2.1.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011URgT9hYuNrXeCvzjnqRxJ
2026-07-03 13:34:34 +02:00
..
2026-03-02 00:36:23 +01:00
2026-03-03 08:38:42 +01:00

pm-product-discovery

Product discovery skills for PMs: ideation, experiments, assumption testing, feature prioritization, and customer interview synthesis.

Skills (13)

  • analyze-feature-requests — Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.
  • brainstorm-experiments-existing — Design experiments to test assumptions for an existing product.
  • brainstorm-experiments-new — Design lean startup experiments (pretotypes) for a new product.
  • brainstorm-ideas-existing — Brainstorm product ideas for an existing product using multi-perspective ideation (PM, Designer, Engineer).
  • brainstorm-ideas-new — Brainstorm feature ideas for a new product in initial discovery.
  • identify-assumptions-existing — Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility.
  • identify-assumptions-new — Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team.
  • interview-script — Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections.
  • metrics-dashboard — Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds.
  • opportunity-solution-tree — Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.
  • prioritize-assumptions — Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each.
  • prioritize-features — Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment.
  • summarize-interview — Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items.

Commands (5)

  • /pm-product-discovery:brainstorm — Brainstorm product ideas or experiments from PM, Designer, and Engineer perspectives — for existing or new products.
  • /pm-product-discovery:discover — Run a full product discovery cycle — from ideation through assumption mapping to experiment design.
  • /pm-product-discovery:interview — Prepare a customer interview script or summarize an interview transcript into structured insights.
  • /pm-product-discovery:setup-metrics — Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thresholds.
  • /pm-product-discovery:triage-requests — Analyze, categorize, and prioritize a batch of feature requests from customers or stakeholders.

Author

Paweł Huryn — The Product Compass Newsletter

License

MIT