to-prd

Generate a PRD from conversation context and publish it to the project issue tracker.

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

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 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 architectural seams for testing the feature and proposes new seams at the highest possible level, confirmed with the user. - 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 codebase, invoke this Skill to produce a ready-to-implement PRD ticket without writing any documentation by hand. ## 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 turn a conversation into a PRD?

Invoke the Skill after discussing the feature with the AI. It synthesizes the existing conversation context and codebase exploration into a structured PRD with problem statement, user stories, and implementation decisions, without asking you new questions.

How do I publish a PRD to an issue tracker automatically?

The Skill writes the PRD using its built-in template and publishes it directly to the project issue tracker, applying the ready-for-agent triage label so no additional triage step is needed.

What sections does the 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 by running /setup-matt-pocock-skills. Without that setup, the Skill cannot publish the PRD or apply the correct labels.

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

Avoid it when the feature has not been discussed enough to define user stories and implementation decisions, since the Skill does not interview the user. It also checks test seams with you, so it is unsuitable for fully unattended documentation runs.