to-prd

Transform conversation context into a structured PRD and publish it to the issue tracker.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill to-prd-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/to-prd
Command: npx skills add https://github.com/haryelramalho/skills --skill to-prd-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an already-discussed feature request into a polished PRD without forcing the user through another interview, saving time when the context is already in the conversation.

Core Features & Use Cases

  • Synthesizes the current discussion and repo context into a structured PRD.
  • Recommends testing seams and keeps them as few and as high-level as possible.
  • Publishes the PRD to the issue tracker with the ready-for-agent triage label.
  • Useful for feature planning, scoped implementation handoff, and work item creation.

Quick Start

Ask the skill to turn this 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 turn existing feature discussions into a product requirements document?

Transform existing conversation context into a product requirements document by synthesizing the current discussion and repository context into a structured PRD. This process skips redundant interviews when feature planning context is already available in the conversation.

Can I publish user stories directly to an issue tracker from a chat conversation?

Yes, you can publish user stories directly to an issue tracker. The skill generates extensive user stories, applies ready-for-agent triage labels, and creates work items without requiring manual data entry or copy-pasting.

How do I generate implementation handoff documents with testing seams?

Generate implementation handoff documents by selecting high-level testing seams and aligning the domain glossary. The skill recommends keeping testing seams as few and high-level as possible for scoped implementation handoff.

Does this PRD synthesis tool require a separate interview or questionnaire?

No, it does not require a separate interview or questionnaire. It relies on existing conversation context and repo exploration to synthesize the PRD, saving time when the problem has already been discussed.

What is the best way to prepare issue tracker work items for agent triage?

The best way to prepare work items for agent triage is to synthesize the discussion into a structured PRD and publish it to the issue tracker with a ready-for-agent triage label attached.

When should I avoid using automated PRD synthesis for product planning?

Avoid using automated PRD synthesis when the feature request has not been previously discussed. The process requires existing conversation context and domain glossary alignment to generate a publishable PRD.