write-a-prd

Generate Product Requirements Documents with problem statements, user stories, and design decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mnadalc/dotfiles --skill write-a-prd-mnadalc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/mnadalc/dotfiles/tree/main/.ai/skills/write-a-prd
Command: npx skills add https://github.com/mnadalc/dotfiles --skill write-a-prd-mnadalc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) by guiding users through a structured process of defining problems, solutions, and implementation details.

Core Features & Use Cases

  • Problem Definition: Captures detailed user problems and potential solutions.
  • Requirement Gathering: Facilitates in-depth interviews to refine requirements and identify dependencies.
  • Module Design: Helps in sketching out necessary modules and defining their interfaces.
  • PRD Generation: Formats requirements into a standard PRD template for submission as a GitHub issue.

Quick Start

Use the write-a-prd skill to start creating a PRD for a new feature.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I generate a PRD from user needs?

To generate a PRD from user needs, the skill systematically elicits problem statements, designs solutions, drafts user stories, and defines implementation decisions. It facilitates iterative refinement through interviews to ensure alignment before formatting the final product requirements document.

What is the best way to structure user stories and module design for software documentation?

Structuring user stories and module design for software documentation involves capturing detailed problem definitions, sketching out necessary modules, and defining their interfaces. This ensures requirements gathering accurately reflects the solution design before formal PRD generation.

Can I use this to refine requirements through user interviews and codebase exploration?

Yes, you can refine requirements through user interviews and codebase exploration. The process facilitates in-depth interviews to identify dependencies and iteratively refine requirements, ensuring the problem statement and solution design align before generating the PRD.

Does the generated product requirements document format work for GitHub issue submission?

Yes, the generated product requirements document is formatted into a standard PRD template specifically designed for submission as a GitHub issue. This streamlines transitioning from software design and requirement gathering directly into development tracking.