to-prd

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

11|2|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/oskrgab/petrodb --skill to-prd-oskrgab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/oskrgab/petrodb/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/oskrgab/petrodb --skill to-prd-oskrgab

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 current conversation context and codebase understanding into a complete PRD and publishes it directly to the project issue tracker with the correct triage label. ## Core Features & Use Cases - Context Synthesis: Converts the existing conversation and codebase exploration into a PRD without re-interviewing the user. - Module Planning: Identifies deep, testable modules to build or modify and confirms scope with the user before writing. - Structured PRD Template: Produces problem statement, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope sections. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the needs-triage label so it enters the normal triage flow. - Use Case: After discussing a new feature with the AI, ask it to write the PRD; it explores the repo, respects ADRs and the domain glossary, drafts the PRD, and files it as a triaged issue. ## Quick Start Turn our 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?

Ask the assistant to turn the current conversation into a PRD. The Skill synthesizes the existing context 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 template 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 deliberately excludes specific file paths and code snippets to avoid becoming outdated.

Does the PRD skill publish to an issue tracker automatically?

Yes, after drafting the PRD it publishes the document to the project issue tracker and applies the needs-triage label so it enters the normal triage flow. 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 first sketches the major modules to build or modify, favoring deep modules with simple testable interfaces, and checks with you on the module list and which modules need tests before writing the PRD.

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

Avoid it when requirements are not yet discussed, since the Skill does not interview the user and only synthesizes existing context. For greenfield ideas with no prior conversation, gather requirements first or write the PRD manually.