to-prd

Convert chat decisions into a Markdown PRD and linked GitHub issue.

15|5|Updated May 17, 2026

Search Tags:#planning #github #requirements #prd #acceptance-criteria #ticketing #open-questions

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesize scattered chat decisions into a durable PRD and trackable GitHub issue to prevent scope drift and rework.

Core Features & Use Cases

Harvest decisions from the conversation and draft a structured PRD with sections like Summary, Problem, Goals, Acceptance Criteria, Open Questions.
Create a GitHub issue from the PRD or export to a local Markdown file, linked to the PRD.
Keep decisions synchronized as new context emerges, and surface open questions for resolution.

Quick Start

Summarize the current discussion into a concise PRD and open a linked GitHub issue.

Frequently Asked Questions about to-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert chat discussions into a structured PRD?▼

To convert chat discussions into a structured PRD, this tool harvests scattered conversation decisions and drafts a document with Summary, Problem, Goals, Acceptance Criteria, and Open Questions sections. It synthesizes product planning context into a concise, durable spec to prevent scope drift.

Can I create a GitHub issue directly from a PRD?▼

Yes, you can create a GitHub issue directly from a PRD. The tool transforms approved product planning decisions into a trackable GitHub issue, ensuring the ticket is linked to the formal requirements document for full traceability and scope management.

What is the best way to track open questions during requirements planning?▼

The best way to track open questions during requirements planning is to extract them into a dedicated PRD section. This surfaces unresolved items for team resolution, keeping decisions synchronized as new context emerges and preventing rework.

Do I need a GitHub repository to generate PRD acceptance criteria?▼

No, you do not need a GitHub repository to generate PRD acceptance criteria. The tool can output a local Markdown file containing your acceptance criteria and UX notes, or create a linked GitHub issue if repository integration is available.

When should I draft a PRD from conversation decisions?▼

You should draft a PRD from conversation decisions when product planning discussions have produced clear decisions but a formal spec is missing. This prevents scope drift by immediately capturing technical constraints and UX notes in a structured format.