skills.rest
jnlanahan
jnlanahanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd

Generate a product requirements document from conversation and codebase context.

Updated Apr 30, 2026
Search Tags:#requirements#product management#functional requirements#prd#non-functional requirements#rollout plan
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill prd-jnlanahan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/2-Define-PRD
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill prd-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered requirements and context into a structured, production-ready PRD that teams can use to align on what to build and how to measure success.

Core Features & Use Cases

  • PRD synthesis from existing context: Produces functional and non-functional requirements, success metrics, risks, and a rollout plan by synthesizing what’s already known.
  • No-interview requirement: Does not ask the user questions during generation; unknowns are marked as <TBD> and captured in Open Questions.
  • Safe handling of missing/insufficient context: Includes pre-flight routing guidance to suggest /discover when customer/problem/scope are too thin, while still allowing the user to proceed after confirmation.
  • Post-flight workflow logging: Updates .claude/progress.md and writes the output to .claude/prd.md for downstream planning.

Quick Start

Run /prd to synthesize the current conversation and codebase understanding into a PRD and write it to .claude/prd.md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a PRD from existing codebase and conversation context?▼

PRD synthesis generates a comprehensive product requirements document by extracting known context, producing structured functional and non-functional requirements, success metrics, risks, and a rollout plan without asking questions.

What's the best way to write product requirements without conducting user interviews?▼

Generating a PRD without interviews works by marking unknowns as <TBD> within an Open Questions section, allowing you to draft requirements immediately while capturing gaps for later resolution.

How do I generate a rollout plan and success metrics for a new feature?▼

Generating a rollout plan and success metrics requires synthesizing existing project context into a structured PRD, which automatically outputs predefined sections for metrics, risks, and phased rollout strategies.

Does PRD generation work when customer and problem scope context is insufficient?▼

PRD generation handles insufficient context by providing pre-flight routing guidance to suggest discovery, while still allowing you to proceed with the draft after confirmation, capturing missing details as <TBD>.

Where are generated product requirement documents and workflow logs saved?▼

Generated product requirements documents are saved as a structured draft at .claude/prd.md, while execution logs and workflow updates are automatically appended to .claude/progress.md for downstream planning.

Related Skills

Explore More Product & Management Skills→
maxenergymaxenergy

to-prd

Generate a structured PRD from the current conversation context and codebase understanding, then publish it to the configured issue tracker workflow.

Community
Advanced
shishishishi
3

scrum-event-sprint-review

Verify Definition of Done and acceptance criteria for sprint increments.

Community
Advanced
InNoobWeTrustInNoobWeTrust
4

ai-ui-generation

Automates AI-generated UI integration into React/Next.js codebases with design constraints and QA checklists.

Community
Advanced
jayhjenkinsjayhjenkins
1

prd-creation

Guide an interactive eight-phase session to create and validate Product Requirements Documents.

Community
Advanced