to-prd

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

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill to-prd-prabaljainn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/prabaljainn/my-claude-code-setup/tree/main/agents/skills/to-prd
Command: npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill to-prd-prabaljainn

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. - Test Seam Planning: Identifies existing architectural seams for testing the feature and proposes new seams at the highest appropriate 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 automatically. - Use Case: After discussing a new feature with the AI and exploring the codebase, invoke the 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 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 with problem statement, user stories, and implementation decisions, without asking you additional questions.

What sections does a generated PRD include?▼

The PRD template includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. Code snippets are only included when they encode a decision more precisely than prose.

Does the PRD skill publish to an issue tracker automatically?▼

Yes, it 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 first via the setup-matt-pocock-skills command.

Why does the skill ask about test seams before writing the PRD?▼

It identifies the architectural seams where the feature will be tested, preferring existing seams at the highest level possible. It confirms these seams with you before writing the PRD so the testing decisions section matches your expectations.

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

Avoid it when the feature is not yet discussed enough to define user stories and implementation decisions, since the skill does not interview you. It also skips detailed file paths and code, so it is unsuitable for low-level technical specs.