prd-creation

Generate Markdown PRDs through a guided question-based process.

15|3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/richardcb/oh-my-gemini --skill prd-creation-richardcb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-creation
Source: https://github.com/richardcb/oh-my-gemini/tree/main/skills/prd-creation
Command: npx skills add https://github.com/richardcb/oh-my-gemini --skill prd-creation-richardcb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) by guiding users through a structured questioning process, ensuring all critical aspects of a new feature are defined before development begins.

Core Features & Use Cases

  • Structured Questioning: Asks targeted questions about the problem, users, functionality, and scope.
  • Automated PRD Generation: Creates a Markdown PRD using a predefined template.
  • Use Case: When starting a new feature, use this Skill to ensure you have a clear, documented understanding of requirements, user stories, and success metrics, preventing scope creep and misaligned development efforts.

Quick Start

Use the prd-creation skill to start defining requirements for a new user authentication feature.

Frequently Asked Questions about prd-creation

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

FAQPage Schema
How do I generate a Product Requirements Document for a new feature?

To generate a Product Requirements Document, use a guided questioning process that collects details on the problem, users, and functionality, then outputs a structured Markdown file covering all critical feature requirements.

What sections should be included in a PRD to prevent scope creep?

A PRD should include a problem statement, goals, user stories, functional requirements, business invariants, and failure states to prevent scope creep and ensure aligned development efforts.

What is a docs-first methodology for product management?

A docs-first methodology enforces defining all necessary product requirements and feature scope in a document before any technical planning or development begins.

Can I automate file naming when creating requirements documentation in Markdown?

Yes, automated file naming can be applied when generating requirements documentation in Markdown, utilizing a standard template to ensure consistent formatting and organization of feature definitions.

What is the best way to collect user stories and functional requirements?

The best way to collect user stories and functional requirements is through targeted, structured questions about the problem and scope, ensuring all critical aspects are defined before development.

When do I need to define business invariants and failure states for a PRD?

You need to define business invariants and failure states for a PRD when starting a new feature, ensuring you have a clear understanding of requirements and success metrics before development begins.