to-prd

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

356|59|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill to-prd-amazingloft999-droid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/amazingloft999-droid/mattpocock-skills/tree/main/skills/engineering/to-prd
Command: npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill to-prd-amazingloft999-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Core Features & Use Cases

  • Synthesize a comprehensive PRD from the conversation, codebase understanding, and ADRs.
  • Publish the PRD to the project issue tracker with appropriate triage labels and routing.
  • Align stakeholders by extracting requirements, success criteria, and milestones from context.

Quick Start

Summarize the current context 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 generate a PRD from conversation context and publish it to an issue tracker?

To generate a PRD, this skill synthesizes current conversation context, codebase understanding, and ADRs into a structured document. It then publishes the PRD to your project issue tracker with a needs-triage label for routing.

What is included in a PRD generated from repository context?

A generated PRD includes requirements, success criteria, milestones, identified modules, and risks. It applies domain glossary vocabulary and respects existing Architecture Decision Records to align stakeholders.

How do I create requirements that align with existing ADRs and stakeholder goals?

You can create aligned requirements by extracting context from the current conversation and applying domain glossary vocabulary. The skill respects ADRs to ensure milestones and risks match stakeholder expectations.

Does the generated PRD automatically enter the project management triage flow?

Yes, the PRD automatically enters the triage flow. Upon publishing to the issue tracker, the skill applies a needs-triage label to ensure the artifact routes correctly into your normal project management process.

Can I use conversation context alone, or do I need codebase understanding for project management PRD generation?

You can use conversation context alone, but the skill also synthesizes codebase understanding and ADRs. This combination ensures the resulting PRD captures comprehensive modules, requirements, and risks.