create-prd

Generate structured PRDs with JTBD, success metrics, and scope boundaries.

42|9|Updated Mar 16, 2026

Search Tags:#planning #templates #prd #product-management #stakeholders #jtbd #requirements-documentation

Ready to run

npx skills add https://github.com/drvoss/everything-copilot-cli --skill create-prd-drvoss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/drvoss/everything-copilot-cli/tree/main/skills/product/create-prd
Command: npx skills add https://github.com/drvoss/everything-copilot-cli --skill create-prd-drvoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams transform vague feature requests into a clear, structured PRD that aligns engineering, product, and stakeholders by capturing Jobs-to-be-Done, success metrics, and explicit scope boundaries.

Core Features & Use Cases

Generates a complete PRD from a feature idea, including JTBD, goals, success metrics, and acceptance criteria.
Provides a reusable template to hand off to design, engineering, and exec teams, improving traceability.
Supports collaboration by linking related issues and previous PRDs to create a connected traceability chain.

Quick Start

Generate a PRD for a feature idea including JTBD, goals, success metrics, and scope boundaries.

Frequently Asked Questions about create-prd

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

FAQPage Schema

How do I create a structured PRD from a vague feature idea?▼

To create a structured PRD from a feature idea, use a standardized template that captures Jobs-to-be-Done, success metrics, and explicit scope boundaries. This transforms vague requests into clear documentation for cross-functional alignment.

What should be included in a product requirements document for engineering handoff?▼

A product requirements document for engineering handoff should include an Overview, Problem Statement, Jobs-to-be-Done, Goals & Metrics, Non-Goals, User Stories, Functional Requirements, Technical Constraints, and Open Questions to ensure traceability.

How do I define scope boundaries and non-goals for product planning?▼

Define scope boundaries and non-goals for product planning by explicitly listing excluded items within a standardized PRD template. This clarifies deliverables and prevents scope creep between product, design, and engineering teams.

Can I use Jobs-to-be-Done framework to align stakeholders on feature success metrics?▼

Yes, you can use the Jobs-to-be-Done framework to align stakeholders by linking specific feature goals to measurable success metrics. This ensures product, design, and engineering teams share a connected traceability chain.

Does this PRD template support linking related issues and previous planning documents?▼

Yes, this PRD template supports collaboration by linking related issues and previous PRDs together. This creates a connected traceability chain that improves alignment across product, design, and engineering teams.

When should I use a standardized PRD template instead of ad-hoc feature documentation?▼

Use a standardized PRD template during early-stage product discovery and cross-functional handoffs instead of ad-hoc documentation. It ensures vague feature requests are systematically translated into clear scope boundaries and functional requirements.