skills.rest
juanelojga
juanelojgaCOMMUNITY
Explore all skills by this author →
GitHub

pm-prd

Generate a structured Product Requirements Document from PM context and research.

Updated Oct 30, 2025
Search Tags:#template#planning#documentation#requirements#prd#product-management#stakeholders
One-click install
npx skills add https://github.com/juanelojga/juanelojga-webpage --skill pm-prd-juanelojga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-prd
Source: https://github.com/juanelojga/juanelojga-webpage/tree/main/.claude/skills/pm-prd
Command: npx skills add https://github.com/juanelojga/juanelojga-webpage --skill pm-prd-juanelojga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams frequently struggle to convert scattered problem statements, research notes, and stakeholder inputs into a cohesive, actionable PRD. This skill automates the assembly of a complete PRD that teams can review and commit to.

Core Features & Use Cases

  • Structured PRD generation: consolidates inputs into a full PRD with executive summary, goals, success metrics, user journeys, requirements, risks, and launch plan.
  • Readiness-driven depth: analyzes PM context to decide between a full PRD, a gap-flagged draft, or a skeleton PRD.
  • Cross-functional alignment: outputs sections tailored for design, engineering, data, and leadership discussions.
  • Use Case: A product manager collects problem statements and user insights and uses this skill to produce a shareable PRD for stakeholder alignment.

Quick Start

Provide your PM context and problem space to trigger automatic PRD generation with this skill.

Frequently Asked Questions about pm-prd

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

FAQPage Schema
How do I create a structured product requirements document from scattered research notes?▼

Creating a structured PRD from scattered notes is done by consolidating problem statements, user insights, and stakeholder inputs into a cohesive spec with goals, requirements, and launch plans.

What should a complete PRD include for stakeholder alignment?▼

A complete PRD for stakeholder alignment should include an executive summary, success metrics, user journeys, detailed requirements, risks, UI mocks, and a launch plan to guide cross-functional discussions.

What is the best way to draft a PRD when product requirements are incomplete?▼

Drafting a PRD with incomplete requirements can be handled by generating a gap-flagged draft or skeleton PRD, which explicitly highlights missing context and open questions for the team to resolve.

How to generate user flows and requirements for a product spec?▼

Generating user flows and requirements for a product spec involves synthesizing collected user insights and brainstorm outcomes into structured sections tailored for design, engineering, and leadership discussions.

Do I need prior PM context to produce a formal product spec?▼

Producing a formal product spec requires prior PM context, as readiness checks analyze your provided problem space and research to determine the appropriate depth, ranging from a skeleton to a full PRD.

Related Skills

Explore More Product & Management Skills→
omeragaakbasomeragaakbas

problem-statement

Articulate user-centered problem statements from interview and persona inputs.

Community
Intermediate
battyejpbattyejp

prd

Generate a structured PRD from a feature description.

Community
Intermediate
melvinv007melvinv007

SE: UX Designer

Generate JTBD analyses, journey maps, and personas for design teams.

Community
Intermediate
leonanpereirapintoleonanpereirapinto
1

cria-techspec

Translate PRDs into technical specifications with architecture and implementation guidance.

Community
Advanced