pm-idea-to-plan

Orchestrates the PM workflow from raw idea to validated, build-ready product plan.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-idea-to-plan-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-idea-to-plan
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/workflows/idea-to-plan
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-idea-to-plan-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams handed a raw idea often jump straight to a polished PRD built on an unvalidated problem and untested willingness to pay. This Skill sequences the full product management ladder — problem framing, discovery, users, riskiest-assumption testing, prioritization, spec, and metrics — so evidence comes before the spec and the plan rests on a de-risked product bet. ## Core Features & Use Cases - Gated PM ladder: Walks seven rungs in order (problem → discovery → personas/JTBD → assumption test → prioritization → spec → metrics), classifying each as core, offer, or skip based on context. - Context profiling: Establishes stakes, reversibility, stage, market maturity, and existing evidence once, then calibrates discovery and testing rigor accordingly. - Validation handoff: Passes the finished plan to a product-review step that runs assumption-rigor and artifact-specific audits, returning one prioritized report. - Use Case: A founder says "I have an app idea, where do I start?" The Skill frames the problem, runs proportionate discovery, designs a painted-door test for the riskiest adoption assumption, and only then produces a proportionate spec. ## Quick Start Take me from my raw product idea to a build-ready plan, starting with the problem and ending with a validated spec.

Frequently Asked Questions about pm-idea-to-plan

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

FAQPage Schema
How do I turn a product idea into a build-ready plan?▼

Start by framing the problem as an evidence-backed gap, then run proportionate discovery, define users from that evidence, test the riskiest assumption, prioritize the first slice, and only then write the spec. This Skill sequences those steps and gates each one.

When should I write a PRD during product planning?▼

Write the PRD last, after the problem is framed, discovery evidence exists, and the riskiest assumption has a falsifiable test. A spec written before that evidence rests on an unvalidated bet, so this Skill keeps the spec proportionate to what is actually known.

What is a riskiest-assumption test in product management?▼

It is the cheapest experiment that falsifiably tests the leap-of-faith belief that would sink the idea if wrong, with pre-set success criteria. For most new ideas this is a painted-door, concierge, or pre-sell test checking real adoption or willingness to pay before code is written.

When should I not use an idea-to-plan orchestration workflow?▼

Skip it when you need one specific artifact like a PRD or prioritization matrix — trigger that skill directly instead. It also stops at a validated plan, so vision, competitive analysis, roadmap, and go-to-market work belong to a separate strategy arc.

How does market maturity change product discovery?▼

In a crowded category, the riskiest assumption is rarely whether you can build it — it is switching cost and adoption, meaning why users would leave the incumbent. Discovery should then prioritize switching-cost evidence and competitive analysis becomes a strong next offer.