skills.rest
skillvee
skillveeCOMMUNITY
Explore all skills by this author →
GitHub

prd

Turn vague feature ideas into a structured PRD saved to tasks/prd-[feature-name].md.

Updated Aug 23, 2026
Search Tags:#documentation#handoff#prd#project-management#product-requirements#clarifying-questions#feature-planning
One-click install
npx skills add https://github.com/skillvee/simulator --skill prd-skillvee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/skillvee/simulator/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/skillvee/simulator --skill prd-skillvee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to convert vague feature ideas into clear, interdependent requirements that guide design, development, and testing.

Core Features & Use Cases

  • Draft a structured PRD that can be converted into GitHub issues or tickets for Ralph to execute.
  • Ask targeted clarifying questions to surface goals, scope, success criteria, and constraints.
  • Save the PRD to a versioned location (tasks/prd-[feature-name].md) for traceability and handoff.

Quick Start

Provide a feature description and I will generate a structured PRD draft saved to 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 draft a structured PRD from a vague feature idea?▼

Generate a structured PRD by providing a feature description; the tool asks clarifying questions to surface scope and success criteria, then saves a complete requirements document to tasks/prd-[feature-name].md.

What should a product requirements document include for engineering handoff?▼

For engineering handoff, a product requirements document should include goals, user stories, functional and non-functional requirements, and technical considerations to ensure clear interdependent development guidelines.

What is the best way to plan features and define project scope before development?▼

Define project scope before development by using targeted clarifying questions to extract goals, constraints, and success criteria, which are then structured into a comprehensive PRD for traceability.

Can I convert a PRD into GitHub issues or tickets for project management?▼

Yes, the generated PRD is structured specifically to be converted into GitHub issues or tickets, allowing seamless handoff and execution across product and engineering workflows.

Does feature planning work without specifying technical constraints upfront?▼

Feature planning works without upfront technical constraints because the process asks targeted clarifying questions to actively surface goals, scope, and constraints during the PRD drafting phase.

Related Skills

Explore More Product & Management Skills→
smallnestsmallnest
207

prd

Generate a structured product requirements document in Markdown from a feature idea.

Community
Advanced
ch-yang1273ch-yang1273

speckit-taskstoissues

Convert tasks from tasks.md into GitHub issues via the GitHub MCP server.

Community
Intermediate
DavidLam-ossDavidLam-oss
283

openprd-requirement-intake

Route product requirements into L0, L1, or L2 development workflows.

Community
Advanced
jsegovjsegov
20

prd-template

Generate a structured project requirements document with standard sections and acceptance criteria.

Community
Intermediate