prd

Create structured product requirements documents with user stories and success metrics.

Updated May 8, 2026
One-click install
npx skills add https://github.com/mmartinsoliv/dotfiles --skill prd-mmartinsoliv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mmartinsoliv/dotfiles/tree/main/agents/skills/prd
Command: npx skills add https://github.com/mmartinsoliv/dotfiles --skill prd-mmartinsoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a vague feature idea into a clear, implementation-ready product requirements document so teams can align on scope, goals, and success criteria before building.

Core Features & Use Cases

  • Clarifying Questions: It asks 3 to 5 essential multiple-choice questions to resolve ambiguity before drafting the PRD.
  • Structured PRD Writing: It produces a complete markdown PRD with overview, goals, user stories, functional requirements, non-goals, success metrics, and open questions.
  • Scope Control: It keeps planning focused and explicitly avoids implementation work, making it useful for feature kickoff, discovery sessions, and AI-assisted product planning.

Quick Start

Tell the PRD skill what feature you want to plan, answer its clarifying questions, and let it generate a structured PRD in the tasks folder.

Frequently Asked Questions about prd

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

FAQPage Schema
What do I need to write a product requirements document for a new feature?

To generate a product requirements document, you simply provide a feature idea. The skill asks 3 to 5 clarifying multiple-choice questions to resolve ambiguity, then drafts a structured PRD covering scope, goals, and success metrics.

How do I define scope and goals for feature planning?

You define scope and goals by answering the skill's clarifying questions. It then outputs a structured PRD that explicitly outlines functional requirements, user stories, and non-goals to keep project kickoff focused.

What is the best way to create structured user stories for a project kickoff?

The best way to create structured user stories is to use a PRD skill that formats them within a markdown document. It applies requirements discovery to generate numbered functional requirements and boundaries for your feature planning.

Can I use this for feature planning without writing code?

Yes, you can use this for feature planning without writing code. The skill explicitly avoids implementation work and focuses on requirements discovery, making it useful for aligning teams on scope and boundaries before building.

How do I handle open questions when drafting product requirements?

You handle open questions by letting the PRD skill identify and list them. The generated markdown document includes a dedicated section for open questions alongside success metrics and non-goals to ensure team alignment.

Does the PRD generator output markdown files for requirements discovery?

Yes, the PRD generator outputs a markdown file saved as tasks/prd-[feature-name].md. It structures the requirements discovery results into a complete document with overview, goals, and functional requirements.