create-prd

Name: create-prd
Availability: InStock
Author: petrsimonidesxart

Generate a lean PRD with vision, user problem, and scope boundaries.

Updated Mar 8, 2026

Search Tags:#scoping #documentation #strategy #alignment #prd #product-management

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill create-prd-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/discovery/create-prd
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill create-prd-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce a concise PRD that clarifies product vision, user problem, value hypothesis, and success metrics to align cross-functional teams.

Core Features & Use Cases

Lean PRD generation: captures Vision, User Problem, Target Users, Value Hypothesis, Success Metrics, and Scope/Constraints.
Canonical structure: outputs in a consistent template to enable rapid iteration and handoff.
Use Case: when starting a new product or major initiative, teams can generate a ready-to-review PRD for stakeholder alignment.

Quick Start

Provide a brief product context and user problem, and the Skill will generate a lean PRD draft.

Frequently Asked Questions about create-prd

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

FAQPage Schema

How do I write a lean PRD to align cross-functional teams on product vision?▼

To write a lean PRD for cross-functional alignment, define the product vision, user problem, target users, value hypothesis, success metrics, and scope boundaries. This approach clarifies strategic uncertainty and guides planning for new products or major initiatives.

When do I need to generate a product requirements document for a new initiative?▼

You need to generate a product requirements document when starting a new product, launching a major initiative, or facing strategic uncertainty. It guides cross-functional alignment and planning by clarifying vision, user problems, and scope boundaries.

What is the best way to document scope boundaries and success metrics for product management?▼

The best way to document scope boundaries and success metrics is using a canonical PRD template. This lightweight structure captures vision, user problems, target users, and value hypotheses to enable rapid iteration and stakeholder handoff.

How to create a lightweight PRD draft from brief product context?▼

To create a lightweight PRD draft, provide brief product context and a user problem. The system then generates a canonical markdown document capturing vision, value hypothesis, success metrics, and constraints for stakeholder review.

Does generating a lean PRD require predefined success metrics and value hypotheses?▼

Generating a lean PRD does not strictly require predefined metrics, but capturing value hypotheses and success metrics is essential. Providing initial product context and user problems allows the draft to articulate these elements for alignment.

What format does the generated product requirements document use for handoff?▼

The generated product requirements document uses a canonical markdown template. It outputs to a structured file path, enabling rapid iteration, consistent structure, and seamless handoff for cross-functional stakeholder review.