skills.rest
DaRipper91
DaRipper91COMMUNITY
Explore all skills by this author →
GitHub

prd-drafter

Generate Product Requirements Documents with structured templates and interrogation workflows.

Updated Aug 23, 2026
Search Tags:#project management#scoping#documentation#feature definition#prd#product requirements
One-click install
npx skills add https://github.com/DaRipper91/gemini-termux-migration --skill prd-drafter-daripper91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-drafter
Source: https://github.com/DaRipper91/gemini-termux-migration/tree/main/AI_Knowledge_Base/Planning_and_Architecture/prd-drafter
Command: npx skills add https://github.com/DaRipper91/gemini-termux-migration --skill prd-drafter-daripper91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents "Jerry-work" by forcing users to define clear requirements, scope, and goals for new features or projects before coding begins, ensuring robust engineering over guesswork.

Core Features & Use Cases

  • Automated PRD Generation: Drafts comprehensive Product Requirements Documents based on user prompts.
  • Structured Requirements: Enforces a clear PRD template including objectives, scope, user journeys, and metrics.
  • Use Case: When a vague request like "Improve the user dashboard" is given, this Skill will interrogate the need, define the scope, and generate a formal PRD for the engineering team.

Quick Start

Use the prd-drafter skill to create a PRD for a new user authentication feature.

Frequently Asked Questions about prd-drafter

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

FAQPage Schema
How do I write a product requirements document for a new feature?▼

To write a product requirements document, use an interrogation-driven workflow to define project scope, goals, and user journeys, generating a standardized PRD template for clear communication between product and engineering teams.

What is the best way to define project scope before development begins?▼

The best way to define project scope is through structured requirement gathering that resolves ambiguity, preventing guesswork by enforcing clear objectives, user journeys, and metrics before coding starts.

Can I use an automated PRD generator for vague feature requests?▼

Yes, an automated PRD generator can take vague feature requests, interrogate the specific needs, define the scope, and draft a comprehensive formal document for the engineering team.

How does an interrogation-driven workflow help with feature definition?▼

An interrogation-driven workflow helps feature definition by forcing users to answer structured questions, resolving ambiguity, and ensuring robust engineering requirements are established over guesswork.

What should be included in a standardized PRD template for engineering teams?▼

A standardized PRD template should include clearly defined objectives, project scope, user journeys, and metrics to facilitate structured requirement gathering and ensure clear communication across teams.

Related Skills

Explore More Product & Management Skills→
pinkroosteraipinkroosterai
1

pm-brainstorm

Generate actionable feature requests from user input, web research, and codebase analysis.

Community
Advanced
dhar174dhar174
1

breakdown-epic-pm

Translate user requests into a complete Epic PRD with standard sections.

Community
Advanced
oletizioletizi

feature-setup

Create a feature branch, worktree, and documentation skeleton with templates.

Community
Intermediate
1479089714790897
7

kwp-product-management-write-spec

Generate structured product requirement documents from unstructured problem statements.

Community
Intermediate