to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/unnxt30/skills --skill to-prd-unnxt30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/unnxt30/skills/tree/main/to-prd
Command: npx skills add https://github.com/unnxt30/skills --skill to-prd-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long planning conversation into a structured Product Requirements Document is tedious and error-prone. This Skill synthesizes the existing conversation context and codebase understanding into a complete PRD and publishes it directly to the project issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the current conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Module Planning: Identifies deep, testable modules to build or modify and confirms them with the user before writing the PRD. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After discussing a new feature with the AI and exploring the repo, invoke this Skill to produce a ready-to-implement PRD issue that respects the project's domain glossary and ADRs. ## Quick Start Ask the AI to turn the current conversation into a PRD and publish it to the issue tracker.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I create a PRD from an AI conversation?

Invoke the to-prd skill after discussing the feature. It synthesizes the existing conversation context and codebase exploration into a structured PRD without asking additional interview questions, then publishes it to the issue tracker.

What sections does a generated PRD include?

The PRD includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. It avoids specific file paths and code snippets except for decision-rich prototype excerpts.

Does the PRD skill require setup before use?

Yes, the issue tracker and triage label vocabulary must be configured first. Run /setup-matt-pocock-skills if this configuration has not been provided, otherwise publishing and labeling will not work.

Can I review the module plan before the PRD is written?

Yes, the skill sketches the major modules to build or modify and checks with you that they match expectations. It also asks which modules you want tests written for before drafting the PRD.

When should I not use conversation-to-PRD generation?

Avoid it when requirements are not yet discussed, since the skill does not interview the user and only synthesizes existing context. For greenfield ideas with no prior conversation, gather requirements through discussion first.