skills.rest
lucidlabs-hq
lucidlabs-hqOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-prd

Generate a structured Product Requirements Document from project inputs.

2|1|Updated Jan 27, 2026
Search Tags:#planning#documentation#ai-agent#prd#stakeholders#product-requirements#executive-summary
One-click install
npx skills add https://github.com/lucidlabs-hq/agent-kit --skill create-prd-lucidlabs-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/lucidlabs-hq/agent-kit/tree/main/.claude/skills/create-prd
Command: npx skills add https://github.com/lucidlabs-hq/agent-kit --skill create-prd-lucidlabs-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a structured Product Requirements Document (PRD) from project discussions, ensuring a single source of truth for requirements.

Core Features & Use Cases

  • Extracts project context and inputs (name, domain, objectives) from conversation to seed the PRD.
  • Generates standard PRD sections and templates aligned with Agent Kit standards.
  • Supports versioning and safe overwrite prompts when a PRD already exists.

Quick Start

Provide project context (name, domain, MVP) and trigger PRD generation to produce .claude/PRD.md

Frequently Asked Questions about create-prd

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

FAQPage Schema
How do I generate a Product Requirements Document from existing project discussions?▼

A PRD should include an Executive Summary, Vision, Problem, MVP Scope, User Stories, Feature Specification, Domain Model, API Specification, and Success Criteria. These standard sections ensure a single source of truth for stakeholders.

What is the best way to structure an AI agent specification within product requirements?▼

Structuring an AI agent specification requires defining its domain model, feature behaviors, and API interactions within the PRD. This ensures agent capabilities align with user stories and implementation phases for coherent product development.

Can I automatically create PRD documentation without losing existing file data?▼

You need to provide high-level project context like the product name, domain area, and MVP definition. This conversation context seeds the document generation without requiring pre-formatted technical specifications or external dependencies.

What limitations exist when defining MVP scope and implementation phases in a PRD?▼

Defining MVP scope depends entirely on the clarity of your conversation inputs and stated objectives. Vague project context will limit the precision of generated implementation phases, user stories, and success criteria in the final document.

Related Skills

Explore More Product & Management Skills→
unicorn-pluginsunicorn-plugins
21

create

Initialize project directories, generate domain-context.yaml, and create GitHub repositories.

Official
Advanced
Prat011Prat011
1.5k

notion-spec-to-implementation

Convert Notion specs into implementation plans with tasks and milestones.

Community
Advanced
battyejpbattyejp

prd

Generate a structured PRD from a feature description.

Community
Intermediate
menkesumenkesu
389

exec-comms

Draft executive memos using Amazon 6-pager, Stripe memo, and SCQA frameworks.

Community
Intermediate