to-prd

Generate a PRD from conversation context and publish it to the issue tracker.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This PRD skill converts the current conversation context into a structured PRD, enabling rapid alignment with stakeholders and consistent documentation.

Core Features & Use Cases

  • Generate a complete PRD from discussion context, ADRs, and architectural notes.
  • Ensure the PRD follows the project glossary and ADR references for terminology consistency.
  • Publish the PRD to the project issue tracker with appropriate triage and labels to track progress.

Quick Start

Convert the current conversation context into a structured PRD ready for publishing.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I turn a conversation into a PRD for my issue tracker?

To turn a conversation into a PRD, the skill extracts current context and codebase understanding to draft a complete, publish-ready product requirements document with proper triage labels.

How do I generate a PRD from ADRs and architectural notes?

You can generate a PRD from ADRs by processing ongoing discussions and architectural plans, ensuring the output references ADR decisions and follows the project glossary for terminology consistency.

What's the best way to align stakeholders using a structured PRD?

The best way to align stakeholders is generating a structured PRD that translates codebase understanding and discussion context into clear requirements ready for issue tracker publication.

Does the PRD generation process support custom glossary terminology?

Yes, the PRD generation process satisfies requirements to follow the project glossary, incorporating specific terminology directly into the drafted product requirements document.

Can I publish a PRD directly to an issue tracker with triage labels?

Yes, you can publish a PRD directly to the chosen issue tracker, automatically applying proper triage labels to track project progress and align stakeholders.

What is included when drafting a PRD from codebase understanding?

Drafting a PRD from codebase understanding includes incorporating ADR references, following the PRD template, and applying glossary terminology to create complete project documentation.