skills.rest
mdmagnuson-creator
mdmagnuson-creatorCOMMUNITY
Explore all skills by this author →
GitHub

prd

Generate a structured PRD saved to docs/drafts/prd-[feature-name].md from user input and project context.

Updated Feb 20, 2026
Search Tags:#documentation#prd#project-management#product-requirements#feature-planning#requirements-spec
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill prd-mdmagnuson-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/prd
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill prd-mdmagnuson-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a comprehensive Product Requirements Document (PRD) for a new feature, enabling teams to plan, communicate, and implement features with a clear spec.

Core Features & Use Cases

  • Reads the project context from docs/project.json (if it exists) to tailor acceptance criteria, constraints, and success metrics.
  • Interacts with the user to capture a feature description and asks 3-5 essential clarifying questions to bound scope.
  • Identifies external service dependencies and credential timing, then outputs a structured PRD saved to docs/drafts/prd-[feature-name].md.
  • Produces a PRD with the defined sections, stack-aware acceptance criteria, and scope considerations mapped from project metadata.

Quick Start

Describe the feature you want and I will guide you through clarifying questions to generate a draft PRD.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a product requirements document from a feature idea?▼

A product requirements document outlines feature scope, dependencies, and acceptance criteria. This tool generates a structured PRD by asking 3-5 clarifying questions and saves the draft to docs/drafts/prd-[feature-name].md.

What's the best way to define feature scope and acceptance criteria for project planning?▼

To define feature scope and acceptance criteria, describe your feature and answer 3-5 clarifying questions. The tool reads docs/project.json to tailor stack-aware acceptance criteria and scope considerations.

Can I use project metadata to tailor product requirements for my existing stack?▼

Yes, you can tailor product requirements using project metadata. The tool reads docs/project.json if it exists, using project context to generate stack-aware acceptance criteria and map scope considerations.

Does a product requirements document include external service dependencies and credential timing?▼

Yes, the generated product requirements document identifies external service dependencies and credential timing. It captures these requirements alongside scope and acceptance criteria during the interactive question phase.

What should I not expect in a PRD draft regarding implementation details?▼

You should not expect implementation details in a PRD draft. The tool explicitly keeps implementation out of scope, focusing the document on product requirements, scope boundaries, and acceptance criteria.

Related Skills

Explore More Product & Management Skills→
Kuba312Kuba312

10x-tech-stack-selector

Analyze a PRD to recommend a technology stack from a predefined registry.

Community
Advanced
richardwurichardwu
2

prd

Generate structured markdown PRDs with user stories and acceptance criteria.

Community
Intermediate
nrminornrminor

prd

Generate a structured PRD with clarifying questions and save it to a markdown file.

Community
Basic
saboteur-labssaboteur-labs

spec-writer

Draft structured feature specifications through guided clarifying questions.

Official
Intermediate