prd

Clarify product requirements through guided dialogue and generate structured Planner commands.

Updated Aug 23, 2026

Search Tags:#planning #requirements #discovery #product definition #user stories #structured input

Ready to run

npx skills add https://github.com/msageha/maestro_v2 --skill prd-msageha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/msageha/maestro_v2/tree/main/templates/skills/orchestrator/prd
Command: npx skills add https://github.com/msageha/maestro_v2 --skill prd-msageha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clarifies ambiguous user requests by engaging in a dialogue to define requirements, ensuring that the information passed to the Planner is structured and actionable.

Core Features & Use Cases

Requirement Clarification: Guides users through a structured questioning process to define problems, success criteria, constraints, scope, and priorities.
Planner Command Generation: Translates clarified requirements into a structured format suitable for delegation to a Planner skill.
Use Case: A product manager has a vague idea for a new feature. This skill helps them articulate the "what," "why," and "how" of the feature, producing a clear brief for the development team's planner.

Quick Start

Use the prd skill to help structure requirements for a new user authentication system.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I structure vague product requirements into actionable user stories?▼

To structure vague product requirements into actionable user stories, you need a guided dialogue that clarifies problem statements, success criteria, constraints, scope, and priorities. This process translates ambiguous feature ideas into a structured brief defining the what and why for development planning.

What is the best way to clarify ambiguous feature requests for a development team?▼

The best way to clarify ambiguous feature requests is through a structured questioning process focused on product definition. By defining problems, success criteria, and constraints upfront, you ensure the information passed to the planner is fully structured and actionable.

How do I define scope and priorities for a new product feature?▼

You define scope and priorities for a new product feature by engaging in a requirement discovery dialogue. This structured input process guides you through articulating specific constraints and success criteria, ensuring the final scope reflects the core problem statement.

Can I generate a structured planner command from initial requirement discovery?▼

Yes, you can generate a structured planner command from initial requirement discovery. The clarified requirements, including scope and priorities, are translated into a structured format suitable for direct delegation to a Planner skill for execution.

Does requirement discovery work for initial product definition phases?▼

Requirement discovery works specifically for initial product definition phases. It applies to the early stages of requirement gathering by helping product managers articulate the what, why, and how of a feature before any technical planning begins.