skills.rest
IsKenKenYa
IsKenKenYaCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

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

Updated May 11, 2026
Search Tags:#requirements#issue tracker#user stories#prd#product planning#repo synthesis
One-click install
npx skills add https://github.com/IsKenKenYa/Commory --skill to-prd-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/IsKenKenYa/Commory/tree/main/.windsurf/skills/to-prd
Command: npx skills add https://github.com/IsKenKenYa/Commory --skill to-prd-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert messy, incomplete conversation context into a structured PRD that stakeholders can review quickly, without manually writing everything from scratch.

Core Features & Use Cases

  • PRD synthesis from current context: Produces a complete PRD draft based on what the agent already knows about the repo and the current conversation.
  • Module-oriented implementation planning: Breaks down the likely modules and decisions needed to deliver the requested capability, including extraction of deep, testable components.
  • Issue-ready output: Writes the PRD using the provided PRD template and publishes it to the project issue tracker with the required triage label.

Quick Start

Ask to-prd to generate a PRD from your current conversation context and publish it to the project issue tracker with the ready-for-agent 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 product requirements document?▼

Generating a PRD from conversation context involves synthesizing the current chat history and repository data into a structured document with module breakdowns, implementation decisions, and explicit scope boundaries.

What is the best way to write user stories for a new codebase module?▼

Writing user stories for a new codebase module requires synthesizing an extensive user-stories section that respects the project's domain glossary and relevant ADRs to ensure accurate scope and implementation planning.

How do I publish a generated PRD directly to an issue tracker?▼

Publishing a generated PRD to an issue tracker is done by writing the synthesized document using a provided PRD template and applying a specific triage label like ready-for-agent to the resulting issue.

Does PRD synthesis from conversation context require manual user interviews?▼

PRD synthesis from conversation context does not require manual user interviews; the tool avoids user interviews entirely and relies on synthesizing existing conversation and repository context.

Can I plan module implementation and testing decisions within a PRD?▼

Planning module implementation and testing decisions within a PRD is supported by breaking down the likely modules needed to deliver the requested capability and extracting deep, testable components.

Related Skills

Explore More Product & Management Skills→
tonombtonomb

to-spec

Synthesize conversation context and repository knowledge into structured technical specifications.

Community
Intermediate
flowelflowel

to-prd

Generate a Product Requirements Document from conversation context and publish it to the issue tracker.

Community
Intermediate
huangzidahuangzida
2

to-prd

Convert conversation context into a glossary-aligned PRD for the issue tracker.

Community
Advanced
mmartinsolivmmartinsoliv

to-prd

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

Community
Advanced