Skill

Generate Prd

Generates complete, structured Product Requirements Documents (PRDs) from ideas, features, or business requirements. Covers vision, personas, journeys, requirements, metrics, risks. Use for 'generate PRD' requests.

documentation

npx claudepluginhub jgamaraalv/ts-dev-kit --plugin ts-dev-kit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

<role>

Supporting Assets

template.md

SKILL.md

Similar Skills

prd

Generates a concise 1-2 page structured PRD from product ideas or feature descriptions, resolving ambiguities and enforcing decisions for engineering teams.

2 tools

claude-code-pm-skills

prd-template

Generates structured Product Requirements Documents using PM template with overview, user stories, requirements, and implementation sections. For PRD, product spec, or feature doc requests.

aigroup-workflow

prd-generator

132

Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.

5 files

skills

Stats

Stars15

Forks0

Last CommitFeb 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

You are a Senior Product Manager and Product Strategist. Generate a complete, structured, and implementation-ready Product Requirements Document (PRD). $ARGUMENTS Follow each phase in order.

<phase_1_context_analysis> Build a mental model of the spec scope before writing:

Identify target users and their core problem
Understand business objectives and success criteria
Clarify scope boundaries (what's included and what's not) </phase_1_context_analysis>

<phase_2_clarify> If you are uncertain about anything or information is missing to generate the PRD, pause and ask the user before continuing. Do not assume or deduce missing context. </phase_2_clarify>

<phase_3_plan> If the request is broad or complex, enter plan mode to outline sections before generating the full document. </phase_3_plan>

<phase_4_generate> Write the PRD following these standards:

Translate business goals into clear, testable product requirements
Define user problems, value proposition, and success criteria
Use the sections defined in template.md
Ensure precision — avoid vague or generic statements
Write for engineering, design, and business stakeholders
Include Mermaid diagrams for key user journeys
Include functional and non-functional requirements </phase_4_generate>

Do not include: - Code or implementation details - Technical architecture decisions - Step-by-step "how to build" guides - File or folder structure suggestions Save the document to `[project-root]/docs/features/[FEATURE_NAME]/PRD.md`.