create-prd

Create comprehensive PRDs from product ideas with structured elicitation and MoSCoW prioritization.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-prd-acidicsoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/create-prd
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-prd-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform high-level product ideas into comprehensive PRDs through structured elicitation, market analysis, and prioritized feature definitions, enabling clear handoffs to design and engineering.

Core Features & Use Cases

  • Guided requirements elicitation and vision capture
  • MoSCoW-based feature prioritization and risk assessment
  • Market analysis templates, personas, and competitive framing
  • Non-functional requirements, timelines, and risk management
  • Ready-to-share PRD templates for greenfield or brownfield initiatives

Quick Start

Provide a complete PRD from a product idea by following the skill’s structured prompts.

Frequently Asked Questions about create-prd

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

FAQPage Schema
How do I write a PRD from a high-level product idea?

PRD creation for greenfield initiatives involves guided requirements elicitation to capture product vision, define user personas, and detail market context. This process transforms high-level concepts into comprehensive documents ready for design and engineering handoffs.

What is the MoSCoW method for feature prioritization in requirements planning?

The MoSCoW method categorizes features into Must-have, Should-have, Could-have, and Won't-have buckets. Applying this to requirements planning ensures structured feature prioritization and risk assessment within your product roadmap.

Can I use this PRD template for brownfield product improvements?

Yes, this PRD template applies to both greenfield product initiatives and brownfield improvements. It adapts structured elicitation to capture evolving market context, update user personas, and prioritize new features for existing products.

What should be included in a complete product requirements document?

A complete product requirements document includes an executive summary, user personas, market analysis, prioritized feature specs, non-functional requirements, success metrics, timeline, and risk assessments.

How do I capture non-functional requirements and success metrics during requirements elicitation?

Capture non-functional requirements and success metrics by integrating them directly into the PRD template during structured elicitation. This ensures technical constraints and measurable goals are documented alongside feature prioritization.