skills.rest
ZzAve
ZzAveCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Generate a PRD from conversation context and codebase understanding, then publish it to the issue tracker.

Updated Mar 17, 2026
Search Tags:#project management#issue tracking#product requirements#PRD generation#conversation synthesis
One-click install
npx skills add https://github.com/ZzAve/teambalance-app --skill to-prd-zzave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/ZzAve/teambalance-app/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/ZzAve/teambalance-app --skill to-prd-zzave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill synthesizes the current conversation context and codebase understanding to create a Product Requirements Document (PRD), eliminating the need for additional interviews and streamlining the project issue tracking process.

Core Features & Use Cases

  • Contextual Synthesis: Automatically generate a PRD based on existing conversation and codebase understanding.
  • Issue Tracker Integration: Publish the PRD directly to the project issue tracker with appropriate labels.
  • No Additional Interviews: Save time by not needing to conduct additional interviews or gather information manually.

Quick Start

Execute the 'to-prd' skill to create a PRD for the current conversation context.

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 an existing conversation without conducting user interviews?▼

To generate a PRD from an existing conversation without user interviews, use a skill that synthesizes conversation context and codebase understanding. It automatically drafts the product requirements document for you.

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

Yes, you can publish a generated PRD directly to a project issue tracker. The skill formats the product requirements document and pushes it with appropriate labels for project management tracking.

What context does the PRD generation process use to ensure accuracy?▼

PRD generation uses conversation context, codebase understanding, domain glossaries, and ADRs (Architecture Decision Records) to ensure the product requirements document accurately reflects technical and business constraints.

Does the PRD generation skill require any external dependencies or scripts to run?▼

No external dependencies are required to run the PRD generation skill. It operates using internal scripts to synthesize context and create product requirements documents within your current environment.

What is the best way to create product requirements from a development discussion?▼

The best way to create product requirements from a development discussion is to synthesize the conversation context directly into a PRD. This approach eliminates manual information gathering and streamlines issue tracking setup.

Related Skills

Explore More Product & Management Skills→
JZKK720JZKK720

po-to-prd

Generate a Product Requirements Document from conversation context and codebase understanding.

Community
Intermediate
vm0-aivm0-ai
1.1k

issue-create

Convert conversation context into structured GitHub issues with labels.

Official
Basic
alessioroberto82alessioroberto82

prioritize

Prioritize product features with MoSCoW and generate structured PRDs.

Community
Intermediate
d3mingd3ming

write-a-prd

Draft product requirements documents from user interviews and repository inspection.

Community
Advanced