to-prd

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

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill to-prd-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/to-prd
Command: npx skills add https://github.com/joshhornby/dotfiles --skill to-prd-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an exploratory conversation about a feature into a structured, actionable PRD is tedious and error-prone. This Skill synthesizes the current 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 existing conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies the highest-level testing seams in the codebase, preferring existing seams, and confirms them with the user before writing. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label so it can flow straight into an agent workflow. - Use Case: After discussing a new billing feature with the AI, ask it to produce a PRD; it explores the repo, proposes test seams, writes the full PRD using the project's domain glossary, and files it as a triaged issue. ## Quick Start Ask the AI to turn the current conversation into a PRD and publish it to the project 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 you new interview questions, then publishes it to your issue tracker.

What sections does the 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. It avoids specific file paths and code snippets except for decision-rich prototype excerpts.

Does the PRD skill publish to an issue tracker automatically?

Yes. After writing the PRD, it publishes the document to the project issue tracker and applies the ready-for-agent triage label, so no additional triage step is needed. The tracker and label vocabulary must be configured beforehand.

What are test seams in PRD planning?

Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams and the highest-level seam possible, proposes new ones only at high points, and checks with the user that the seams match expectations before writing the PRD.

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

Avoid it when the feature has not been discussed enough to establish problem, solution, and scope, since the skill does not interview the user. It also requires prior setup of the issue tracker and triage label vocabulary via the setup command.