prd

Generate structured PRDs with goals, user stories, and acceptance criteria.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/baramnim/skill.md --skill prd-baramnim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/baramnim/skill.md/tree/main/prd
Command: npx skills add https://github.com/baramnim/skill.md --skill prd-baramnim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to transform vague feature ideas into detailed, shared requirements. This skill automates that process by generating a structured PRD from user input, clarifying questions, and a defined format that can be handed to engineering and design.

Core Features & Use Cases

  • Generate a complete PRD with sections like Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, Non-Goals, etc.
  • Ask 3-5 clarifying questions to resolve ambiguity before drafting the PRD.
  • Save the PRD to a file at /tasks/prd-[feature-name].md for traceability and handoff.
  • Use cases: planning a new feature, starting a new project, or responding to a request for PRD.

Quick Start

Provide a feature description to generate a complete PRD saved at /tasks/prd-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I turn a feature idea into a product requirements document?▼

To turn a feature idea into a product requirements document, provide a feature description and the skill generates a structured PRD with sections like Introduction, Goals, User Stories, and Acceptance Criteria.

What sections should be included when writing a PRD for a new feature?▼

A PRD for a new feature should include an Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, and Non-Goals to fully guide design and engineering teams.

Can I generate user stories and acceptance criteria from a short feature prompt?▼

Yes, you can generate user stories and acceptance criteria from a short feature prompt. The skill asks 3-5 clarifying questions to resolve ambiguity before drafting the complete specifications.

How do I document functional requirements and non-goals for engineering handoff?▼

To document functional requirements and non-goals for engineering handoff, the skill maps your feature description into structured sections and saves the file at /tasks/prd-[feature-name].md for traceability.

Does this PRD generation approach work for planning entirely new projects?▼

Yes, this PRD generation approach works for planning entirely new projects. It applies to planning new features, evaluating projects, and documenting specifications across product, design, and engineering teams.