to-prd

Convert conversation context and codebase understanding into structured PRDs.

Updated May 5, 2026

Search Tags:#product management #issue tracker #codebase analysis #user stories #prd #product requirements

Ready to run

npx skills add https://github.com/ethan-rio/skills --skill to-prd-ethan-rio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/ethan-rio/skills/tree/main/skills/productivity/to-prd
Command: npx skills add https://github.com/ethan-rio/skills --skill to-prd-ethan-rio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting product requirement documents from scattered conversation threads and codebase knowledge is time-consuming and often leads to missing critical requirements or misaligned project context.

Core Features & Use Cases

Context Synthesis: Automatically compiles existing conversation context and codebase understanding into a structured PRD without requiring follow-up user interviews.
Project Alignment: Ensures all PRD content uses the project's official domain glossary and respects existing architectural decision records (ADRs) for consistency.
Direct Publishing: Posts the finalized PRD directly to the project issue tracker with the correct triage label to enter the standard review workflow. Use Case: If your team has just discussed a new payment processing feature in a chat thread, this skill will automatically compile all discussed requirements, user stories, and implementation decisions into a formal PRD and publish it to your issue tracker for triage.

Quick Start

Use the to-prd skill to turn our current conversation about the new user onboarding flow into a published PRD on 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 turn chat conversation context into a product requirements document?▼

To create a product requirements document from chat context, the skill compiles existing conversation threads and codebase understanding into a structured PRD without requiring follow-up user interviews.

How do I generate user stories and problem statements aligned with project domain glossaries?▼

Generating user stories and problem statements aligned with project domain glossaries involves synthesizing conversation context while respecting existing architectural decision records to ensure project alignment and terminology consistency.

Can I publish product requirements directly to an issue tracker for triage?▼

Yes, you can publish product requirements directly to an issue tracker. The skill posts the finalized PRD with the appropriate triage label to enter the standard review workflow automatically.

What is the best way to draft a PRD without conducting additional user interviews?▼

The best way to draft a PRD without additional user interviews is to synthesize existing conversation context and codebase knowledge automatically, extracting problem statements, implementation decisions, and out-of-scope items directly.

Does generating a PRD from codebase analysis require manual formatting before publishing?▼

Generating a PRD from codebase analysis does not require manual formatting, as the skill structures the content into comprehensive sections including user stories and testing decisions before publishing it to the issue tracker.

When should I not use automated PRD generation from conversation context?▼

You should not use automated PRD generation when a project lacks established architectural decision records or a domain glossary, as the output relies on these existing project artifacts for proper alignment and consistency.