to-prd

Convert conversation context into a PRD and publish it with the needs-triage label.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents vague or incomplete requirements by transforming existing conversation and project context into a complete PRD that can be shared and tracked.

Core Features & Use Cases

  • PRD synthesis from known context: Produces a PRD without interviewing the user, relying on what is already available in the conversation and your understanding of the codebase.
  • Repo-aware module planning: Identifies major modules to build or modify and encourages deeper, testable (“deep”) interfaces.
  • Issue-tracker publishing with triage: Formats the PRD using the provided template and publishes it to the project issue tracker using the needs-triage label.
  • Validation against project vocabulary: Uses the project’s domain glossary and respects ADRs for the area being touched.

Quick Start

Run the to-prd skill to synthesize the current conversation context into a PRD and publish it to the project issue tracker with the needs-triage triage label.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I convert conversation context into a PRD for issue tracker triage?

To convert conversation context into a PRD, the skill synthesizes existing project context and codebase understanding into a publishable document, then publishes it directly to the issue tracker using the needs-triage label without requiring additional user interviews.

Can I generate a PRD without conducting a user interview?

Yes, you can generate a PRD without a user interview when requirements are already derivable from the existing conversation context and codebase, allowing the skill to synthesize the document directly from known information.

How do I ensure my PRD aligns with the project domain glossary and ADRs?

To ensure your PRD aligns with the domain glossary and ADRs, the skill validates the synthesized requirements against the project's established vocabulary and respects architectural decision records for the specific area being modified.

What is the best way to plan modules from existing conversation context?

The best way to plan modules from conversation context is using repo-aware synthesis that identifies major modules to build or modify, encouraging deeper, testable interfaces directly within the generated PRD.

Does PRD generation work when new requirements must be elicited from the user?

PRD generation does not work when new information must be elicited from the user, as the skill is designed strictly for synthesizing existing conversation context and codebase understanding rather than extracting new requirements.

How do I publish a PRD with a needs-triage label to my issue tracker?

To publish a PRD with a needs-triage label, the skill formats the synthesized requirements using a provided template and automatically publishes the document to the project's issue tracker with the triage label attached.