to-prd

Synthesize a structured PRD from conversation context and project files.

7|Updated Mar 4, 2026

Search Tags:#planning #markdown #context #publish #prd #product-requirements #github-issue

Ready to run

npx skills add https://github.com/Davie521/claude-skills --skill to-prd-davie521

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/Davie521/claude-skills/tree/main/plugins/dev-workflow/skills/to-prd
Command: npx skills add https://github.com/Davie521/claude-skills --skill to-prd-davie521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts fragmented discussion and context into a structured PRD to accelerate product planning and reduce back-and-forth.

Core Features & Use Cases

PRD generation: synthesize problem, solution, user stories, and decisions from the current context.
Publish options: publish to GitHub as an issue when gh is configured, or save as a markdown PRD file under docs/prds.
Context-aware: respects existing CONTEXT.md or glossary and surfaces necessary ADRs from docs/adr if present.

Quick Start

Summarize the current conversation and run to-prd to generate and publish a PRD.

Frequently Asked Questions about to-prd

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

FAQPage Schema

How do I generate a PRD from existing conversation context?▼

To generate a PRD from conversation context, the tool synthesizes the current discussion and project details into a structured document covering problem, solution, user stories, and decisions. It automatically structures your fragmented context into a publishable markdown file.

Can I publish a PRD directly to a GitHub issue?▼

Yes, you can publish a PRD directly to a GitHub issue when the GitHub CLI (gh) is configured. If gh is not configured, you can save the PRD as a markdown file under the docs/prds directory instead.

How does PRD generation handle existing project context and ADRs?▼

PRD generation respects existing project context by surfacing CONTEXT.md if present and referencing Architecture Decision Records from docs/adr. This ensures the synthesized output aligns with established project definitions and decisions.

What is the best way to convert planning session notes into a structured PRD?▼

The best way to convert planning session notes into a structured PRD is to summarize the current conversation and run the generation process. It adheres to a standard PRD template to map your notes into problem, solution, scope, and testing sections.

What sections are included in the markdown PRD output?▼

The markdown PRD output includes structured sections for the problem, solution, user stories, decisions, testing, scope, and notes. This ensures the final document covers all necessary product requirements.

Do I need GitHub CLI installed to save a PRD as a markdown file?▼

No, you do not need the GitHub CLI installed to save a PRD as a markdown file. GitHub CLI is only required if you choose to publish the product requirements document directly as a GitHub issue.