pm

Generate structured PRDs with problem hypothesis, success metrics, and MVP scope.

Updated Aug 27, 2026

Search Tags:#planning #discovery #handoff #prd #product-management #prd-creation

Ready to run

npx skills add https://github.com/jforksy/claude-skills --skill pm-jforksy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm
Source: https://github.com/jforksy/claude-skills/tree/main/pm
Command: npx skills add https://github.com/jforksy/claude-skills --skill pm-jforksy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Senior Product Manager Skill helps teams translate vague product ideas into structured PRDs that can be handed to engineering leadership, reducing ambiguity and speeding handoffs.

Core Features & Use Cases

Discovery-driven PRD creation: guides questions to uncover problem scope, user pain, success criteria, and constraints.
CTO-ready handoff: outputs a complete PRD with sections for problem hypothesis, target user, current alternatives, success metrics, full vision, MVP scope, and phased rollout.
Use Case: When proposing a new feature, generate a PRD that a CTO can review and sign off without back-and-forth.

Quick Start

Tell the assistant you want a CTO-ready PRD for a new feature: provide the high-level goal and any constraints.

Frequently Asked Questions about pm

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

FAQPage Schema

How do I create a CTO-ready PRD from a vague product idea?▼

To create a CTO-ready PRD, guide discovery to document problem scope, user pain, and constraints, then output structured sections for problem hypothesis, target user, success metrics, and phased rollout for engineering handoff.

What sections are required for a product management handoff to engineering leadership?▼

A product management handoff requires PRD sections for problem hypothesis, target user, current alternatives, success metrics, full vision, MVP scope, and phased rollout to reduce ambiguity for engineering leadership.

Can I generate a PRD for a new feature proposal without detailed requirements?▼

Yes, you can generate a PRD for a new feature proposal by providing a high-level goal and constraints, and the discovery process will uncover problem scope, user pain, and success criteria automatically.

What is the best way to structure an MVP scope within a product requirements document?▼

The best way to structure an MVP scope is to document it within a full vision section, separating core phased rollout deliverables from broader product requirements to ensure clear engineering handoff.

How does discovery-driven PRD creation improve the product management process?▼

Discovery-driven PRD creation improves the process by guiding questions to uncover problem scope and constraints upfront, reducing ambiguity and speeding up the handoff to engineering leadership.

Does this approach support defining success metrics for new feature proposals?▼

Yes, this approach supports new feature proposals by guiding discovery to define explicit success metrics alongside the problem hypothesis, target user, and MVP scope within the PRD.