product-manager

Synthesize scattered business research into a decision-ready PRD.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wolram/skills --skill product-manager-wolram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/wolram/skills/tree/main/product/product-manager
Command: npx skills add https://github.com/wolram/skills --skill product-manager-wolram

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform scattered sources (reports, decks, notes) into a single, decision-ready PRD that clarifies business rationale, validates hypotheses, and guides next steps.

Core Features & Use Cases

  • Synthesize business research, interviews, and metrics into a cohesive PRD.
  • Distinguish facts, signals, numbers, hypotheses, and gaps to improve decision quality.
  • Write the PRD using the references/business-prd-template.md and surface risks, monetization, and roadmap considerations.

Quick Start

Provide the sources and ask me to generate a business PRD using the business-prd-template.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I turn scattered business research into a decision-ready PRD?

A business PRD distinguishes facts, signals, numbers, hypotheses, and gaps to improve decision quality, ensuring stakeholders can evaluate success criteria and go/no-go gates accurately.

What is the best way to structure a PRD for diverse stakeholders?

A standardized business PRD template ensures cross-functional alignment by separating verified metrics from untested hypotheses and explicitly defining go/no-go gates for implementation.

How do I write a PRD that includes market analysis and a business case?

Integrating market analysis into your PRD requires distinguishing between raw signals and hard numbers, which clarifies the monetization plan and strengthens the overall business rationale.

Can I use this to generate a PRD from raw product notes and decks?

Processing raw notes and decks yields a cohesive PRD that outlines success criteria, monetization considerations, and roadmap priorities without losing the original strategic context.

When do I need a PRD with explicit go/no-go gates and success criteria?

Defining go/no-go gates and success criteria in a PRD ensures that product initiatives are evaluated against distinguished facts and signals before advancing through the implementation roadmap.

Does generating a PRD with this approach work for roadmap prioritization?

By distinguishing strategic gaps from verified numbers, the generated PRD directly informs roadmap prioritization and aligns diverse stakeholders around validated business outcomes.