skills.rest
ian-pascoe
ian-pascoeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd

Generate product requirements documents with user stories, acceptance criteria, and risk analysis.

1|Updated Mar 19, 2026
Search Tags:#acceptance criteria#feature planning#user stories#prd#product requirements#ai product#risk analysis
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill prd-ian-pascoe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/prd
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill prd-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague product ideas into structured, production-ready PRDs so scope, goals, and success criteria are clear before development begins.

Core Features & Use Cases

  • Produces executive summaries, user stories, acceptance criteria, technical specifications, and risk analysis.
  • Supports software systems and AI-powered features that need measurable requirements and evaluation criteria.
  • Useful when launching a new feature, aligning stakeholders, or documenting scope for engineering handoff.

Quick Start

Ask the prd skill to draft a PRD for your feature, including the problem, target users, constraints, and success metrics.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document for AI-powered features?▼

Generating a product requirements document requires translating vague ideas into structured technical specifications, including executive summaries, user stories, and acceptance criteria. This ensures scope, goals, and success criteria are clear before development begins.

What should be included in feature planning for engineering handoff?▼

Feature planning for engineering handoff should include user stories, acceptance criteria, and technical specifications. Defining these elements ensures stakeholders are aligned and scope is documented clearly before development begins.

Can I turn a vague product idea into technical specifications automatically?▼

You can turn vague product ideas into technical specifications by drafting a PRD that includes the problem, target users, constraints, and success metrics. This translates concepts into production-ready specifications for engineering teams.

How do you define evaluation criteria for new feature planning?▼

Defining evaluation criteria for new feature planning involves specifying measurable requirements within the product requirements document. This provides clear success metrics and scope definition for AI-powered features and software systems.

Why do I need phased risk analysis in a product requirements document?▼

Phased risk analysis in a product requirements document identifies potential issues across development stages. It ensures technical specifications and acceptance criteria account for risks, aligning stakeholders before engineering handoff.

Related Skills

Explore More Product & Management Skills→
hemoryhemory

product-brief

Guide product idea capture and generate structured Product Requirements Documents.

Community
Advanced
thavirak-svaythavirak-svay
1

bmad-quick-spec

Automate creation of implementation-ready technical specifications for small software features.

Community
Intermediate
shirulotshirulot

deliver-prd

Generate comprehensive Product Requirements Documents with testable user stories and success metrics.

Community
Intermediate
githubgithub
37.6k

prd

Generate production-grade PRDs with executive summaries, user stories, and technical specifications.

Official
Basic