skills.rest
kalilurrahman
kalilurrahmanCOMMUNITY
Explore all skills by this author →
Website𝕏@krahmanGitHub

prd

Generates a concise one-to-two page PRD from a product idea or feature description.

1|Updated Mar 21, 2026
Search Tags:#documentation#product management#prd#product requirements#generate#mvp scoping
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill prd-kalilurrahman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/prd
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill prd-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product ideas often stay vague, leading to misaligned teams and bloated documentation. This Skill turns a rough product idea or feature description into a sharp, decision-driven PRD of 1-2 pages that engineers, designers, and stakeholders can start building from immediately. ## Core Features & Use Cases - Structured PRD Generation: Produces a complete PRD covering Problem, Target Users, Solution, Success Metrics, Scope, and Risks & Open Questions. - Forced Clarity: Identifies ambiguities in the input and forces concrete decisions, including a mandatory "What we are NOT building" section with real exclusions. - Measurable Metrics: Requires every success metric to include numbers or measurable targets rather than vague goals. - Use Case: A product manager has a rough idea for an integration dashboard. Provide the idea, and receive a saved prd-[product-name].md file with MVP scope, V2 plans, explicit exclusions, and open questions ready for team review. ## Quick Start Ask the assistant to generate a PRD from your product idea or feature description and save it as a Markdown file.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a PRD from a rough product idea?▼

Provide the product idea or feature description as input, and the Skill structures it into Problem, Target Users, Solution, Success Metrics, Scope, and Risks sections. It forces concrete decisions on ambiguities and saves the result as a prd-[product-name].md file.

What sections should a good PRD include?▼

This PRD format includes Problem, Target Users, Solution with explicit exclusions, Success Metrics with measurable targets, Scope split into MVP and V2, and Risks & Open Questions. The "What we are NOT building" section is mandatory.

How long should a product requirements document be?▼

This Skill enforces a maximum of two pages. The constraint forces decision-making; if the document runs longer, it indicates unresolved ambiguity rather than thoroughness.

What happens if my product idea is too vague for a PRD?▼

If the input lacks enough detail to write a clear PRD, the Skill lists the specific questions that need answers first instead of producing a vague document. This prevents building on unclear requirements.

When should I not use a short PRD format?▼

A one-to-two page PRD suits early-stage features and fast-moving teams. Regulated industries or large enterprise programs requiring formal compliance documentation may need more extensive specification formats.

Related Skills

Explore More Product & Management Skills→
NimbalystNimbalyst
25

customer-interview-sim

Simulate customer interviews to practice and refine interview scripts.

Official
Intermediate
kmshihab7878kmshihab7878
6

Scrum Master

Break epics into user stories and plan sprint iterations with velocity metrics.

Community
Advanced
kirvinkirvin

planning-products

Guide product feature definition through problem framing, market research, and scoping.

Community
Intermediate
AvistianAvistian

idea-refine

Refines raw ideas into actionable one-pagers through structured divergent and convergent thinking.

Community
Intermediate