to-prd

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

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill to-prd-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill to-prd-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an exploratory conversation about a feature into a structured, actionable PRD is tedious and often loses context. This Skill synthesizes the current conversation and codebase understanding directly into a complete PRD and publishes it 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 PRD without asking the user to repeat information. - Module Planning: Identifies deep, testable modules to build or modify and confirms scope and test coverage with the user before writing. - Structured PRD Template: Produces a PRD with problem statement, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope notes. - 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 repo, ask it to write the PRD — it drafts the full document using the project's domain glossary and ADRs, then files it as a triaged issue. ## Quick Start Ask the agent 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 the agent. It synthesizes the existing conversation and codebase exploration into a structured PRD without re-interviewing you, then publishes it to the project issue tracker.

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 skill publish the PRD to an issue tracker?▼

Yes, after writing the PRD it publishes the document 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 command.

Can I review the module plan before the PRD is written?▼

Yes, the skill sketches the major modules to build or modify and checks with you that they match expectations. It also asks which modules you want tests written for before drafting the PRD.

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

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