create-prd

Transform ambiguous user requests into structured Product Requirements Documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/msageha/maestro_v2 --skill create-prd-msageha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/msageha/maestro_v2/tree/main/templates/skills/planner/create-prd
Command: npx skills add https://github.com/msageha/maestro_v2 --skill create-prd-msageha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms ambiguous user requests into structured Product Requirements Documents (PRDs), ensuring clarity and actionable planning for software development.

Core Features & Use Cases

  • Requirement Structuring: Organizes vague ideas into clear objectives, success metrics, and user stories.
  • Scope Definition: Explicitly defines what is in and out of scope for a project.
  • Use Case: When a user says "I want to build a better dashboard," this Skill will guide them through defining the dashboard's purpose, target users, key features, and success criteria, creating a solid foundation for the next planning phase.

Quick Start

Use the create-prd skill to convert the request "build a user profile page" into a structured PRD.

Frequently Asked Questions about create-prd

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

FAQPage Schema
How do I structure vague product requests into a PRD?

To structure vague product requests into a PRD, you need to define specific objectives, success metrics, user stories with acceptance criteria, and explicitly list out-of-scope items. This process transforms ambiguous ideas into clear, actionable planning documents for software development.

What is needed to define project scope and requirements for a new feature?

Defining project scope requires explicitly stating what is in and out of scope for the feature. You must also organize the request into clear objectives, measurable success metrics, and user stories to ensure actionable software planning.

Can I convert a simple idea like building a dashboard into a full product requirements document?

Yes, you can convert a simple idea like building a dashboard into a product requirements document. The process guides you through defining the dashboard's purpose, target users, key features, and success criteria to create a solid planning foundation.

When do I need product management documentation for task planning?

You need product management documentation for task planning during the initial requirement gathering and scope definition phases. It ensures clarity by transforming ambiguous user requests into structured PRDs before committing to software development.

What's the best way to write user stories with acceptance criteria for software planning?

The best way to write user stories with acceptance criteria for software planning is to map them directly against defined objectives and success metrics. This ensures every story has clear validation parameters and fits within the explicitly defined project scope.