to-prd

Convert conversation and repository context into a publishable product requirements document.

Updated May 8, 2026

Search Tags:#requirements #synthesis #prd #user-stories #issue-tracker #product-planning

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an existing conversation and repo context into a clear, publishable product requirements document, removing the need to manually assemble scattered notes into a structured plan.

Core Features & Use Cases

Synthesizes the current discussion into a full PRD with problem statement, solution, user stories, implementation decisions, testing decisions, scope, and follow-up notes.
Helps teams move from exploratory conversation to an actionable artifact that can be shared with engineering and tracked in an issue system.
Use it when you already have enough context to draft requirements and want the AI to organize, refine, and publish them without re-interviewing the user.

Quick Start

Ask the assistant 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 convert an existing conversation into a publishable product requirements document?▼

To convert a conversation into a product requirements document, this Skill synthesizes your current context to generate problem statements, user stories, and implementation decisions, then publishes them directly to your issue tracker.

What is the best way to generate user stories from existing repo context without being interviewed?▼

Generating user stories from repo context requires strict adherence to a template without interviewing the user, applying PRD synthesis to your existing discussion to automatically extract and structure ready-for-agent labeled requirements.

How do I publish synthesized PRD planning decisions to an issue tracker?▼

Publishing synthesized PRD planning decisions to an issue tracker is handled automatically by transforming the generated product requirements, scope, and testing decisions into an actionable artifact ready for engineering teams.

Do I need to manually assemble scattered notes into a structured plan for product planning?▼

You do not need to manually assemble scattered notes into a structured plan for product planning, because this Skill removes that requirement by organizing existing exploratory conversation context into a full PRD.

Can I use this to draft requirements if I already have enough context but want AI to organize them?▼

You can use this to draft requirements when you have enough context, as it leverages AI to organize, refine, and publish your product planning decisions without re-interviewing you or requiring additional input.

What limitations exist when synthesizing a PRD from current conversation context?▼

A limitation when synthesizing a PRD from current conversation context is that the Skill requires sufficient existing discussion and repository context to work, as it operates strictly without interviewing the user to gather missing information.