to-prd

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design 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's 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. - Test Seam Planning: Identifies existing or proposed testing seams in the codebase 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 brainstorming a new feature with the agent, ask it to produce a PRD. It explores the repo, respects the domain glossary and ADRs, drafts the PRD from the template, and files it as a triaged issue. ## Quick Start Turn everything we have discussed so far 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 turn a conversation into a PRD?

Invoke the to-prd skill after discussing a 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 the generated PRD include?

The PRD template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. File paths and code snippets are excluded except for decision-rich prototype excerpts.

Does the PRD skill require setup before use?

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

Can I review the PRD before it is published?

The skill checks proposed testing seams with the user before writing the PRD, but the final document is published directly to the issue tracker with the ready-for-agent label and no additional triage step.

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

Avoid it when the feature is still ambiguous or the conversation lacks enough context, since the skill does not interview the user. In those cases, use a brainstorming or discovery skill first to flesh out the design.