prd-generator

Generate a complete Markdown PRD with acceptance criteria and timelines from a product plan file.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mazicimert/RunDom --skill prd-generator-mazicimert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-generator
Source: https://github.com/mazicimert/RunDom/tree/main/.claude/skills/product/prd-generator
Command: npx skills add https://github.com/mazicimert/RunDom --skill prd-generator-mazicimert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to convert a detailed product development plan into a formal Product Requirements Document, leading to misalignment and delays. This skill automates the translation, ensuring a consistent, comprehensive PRD that can be reviewed by stakeholders.

Core Features & Use Cases

  • Automatically convert a product plan into a structured PRD including features, user stories, acceptance criteria, success metrics, and release timelines.
  • Incorporate insights from competitive analysis and market research when available to justify positioning and success metrics.
  • Generate a complete, ready-to-share PRD at docs/PRD.md that can serve as the single source of truth for downstream specifications.

Quick Start

Provide the product development plan file (product-plan-*.md) and I will generate docs/PRD.md from it.

Frequently Asked Questions about prd-generator

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

FAQPage Schema
How do I convert a product plan into a structured PRD with acceptance criteria?

To convert a product plan into a structured PRD, provide your product plan file to extract problem statements, MVP scope, user flows, and Given/When/Then acceptance criteria. It outputs a ready-to-share PRD document with functional and non-functional requirements.

What sections should a product requirements document include for stakeholder review?

A PRD for stakeholder review should include problem statements, MVP scope, positioning, target audience, success metrics, and competitive analysis references. It must also contain functional requirements, user flows, Given/When/Then acceptance criteria, and a release timeline.

Can I generate a PRD automatically from an existing markdown product plan?

Yes, you can generate a PRD automatically from an existing markdown product plan. The tool identifies essential product plan details and outputs a comprehensive PRD file at docs/PRD.md ready for stakeholder review.

How do I add competitive analysis and market research to my PRD success metrics?

To add competitive analysis and market research to your PRD success metrics, include these references in your input product plan. The generated PRD incorporates available market research insights to justify positioning and define success metrics.

What is the best way to write user flows and Given/When/Then acceptance criteria for an MVP?

The best way to write user flows and Given/When/Then acceptance criteria for an MVP is to define the MVP scope in your product plan. The tool translates this into structured user flows and testable acceptance criteria within the PRD.

Does the generated PRD include non-functional requirements and a release timeline?

Yes, the generated PRD includes non-functional requirements and a release timeline. It extracts these details from your product plan to ensure the final document provides a complete specification downstream.