to-prd

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

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

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 modules to build or modify, confirms them with the user, and records architectural decisions without brittle file paths. - 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 your AI assistant, invoke this Skill to produce a ready-to-implement PRD issue that an agent or developer can pick up immediately. ## Quick Start Ask the assistant 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 with your AI assistant. It synthesizes the existing conversation context and codebase exploration into a structured PRD without asking you additional interview questions.

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 so the document stays valid as code evolves.

Does the PRD get published to an issue tracker automatically?

Yes, the skill publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be configured beforehand via the setup-matt-pocock-skills command.

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

Avoid it when requirements are still ambiguous or the user has not yet confirmed module boundaries and testing scope. The skill assumes the conversation already contains enough context to synthesize decisions rather than discover them.

Why does the PRD avoid file paths and code snippets?

File paths and code become outdated quickly as the codebase changes. The skill records architectural decisions, interfaces, and schema changes instead, only inlining prototype snippets when they encode a decision more precisely than prose.