skills.rest
JohannesKonings
JohannesKoningsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-prd

Synthesize conversation and codebase context into a product requirements document and publish it to the issue tracker.

1|Updated Aug 1, 2020
Search Tags:#documentation#workflow automation#github issues#codebase analysis#prd#product requirements#triage
One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill to-prd-johanneskonings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill to-prd-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting product requirements documents (PRDs) from lengthy conversation threads is time-consuming and often leads to missing critical context or misaligned terminology with existing project standards.

Core Features & Use Cases

  • Context Synthesis: Automatically pulls relevant details from prior conversation and codebase understanding to build a complete PRD without requiring additional user interviews.
  • Project Alignment: Ensures all PRD content uses the project's official domain glossary and respects existing architectural decision records (ADRs) for consistency.
  • Direct Publishing: Publishes the finished PRD directly to the project issue tracker with the correct triage label to integrate with existing project workflows.
  • Use Case: For example, after a 30-minute discussion with your engineering team about a new payment processing feature, use this skill to instantly generate a structured PRD and add it to your GitHub issues for triage.

Quick Start

Use the to-prd skill to generate and publish a PRD for the new user onboarding flow we just finalized in our conversation.

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 a conversation without manual drafting?▼

To generate a PRD from a conversation, this skill synthesizes existing discussion context and codebase analysis into a complete product requirements document automatically, without requiring additional user input or interviews.

Can I publish a generated product requirements document directly to GitHub issues?▼

Yes, you can publish a product requirements document directly to GitHub issues. The skill creates the PRD and publishes it to the project issue tracker, applying the correct triage label to integrate with standard project workflows.

How to align new product requirements with existing architectural decision records?▼

To align new product requirements with architectural decision records, the PRD generation process automatically references existing ADRs and the project's domain glossary, ensuring all generated content respects current architectural standards and terminology.

Does generating a PRD from codebase context require additional user interviews?▼

Generating a PRD from codebase context does not require additional user interviews. The skill synthesizes prior feature discussions and existing codebase understanding to build a complete product requirements document instantly.

What is the best way to automate PRD creation for software development workflows?▼

The best way to automate PRD creation for software development workflows is using context synthesis to pull relevant details from prior conversations and codebase analysis, outputting a structured document ready for issue tracker triage.

When should I not use automated PRD generation from conversation context?▼

You should not use automated PRD generation from conversation context when prior feature discussions are missing, or when a project lacks an existing domain glossary and architectural decision records to ensure terminology alignment.

Related Skills

Explore More Product & Management Skills→
JohnRobert-OlanoJohnRobert-Olano

to-prd

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

Community
Intermediate
MatheusBBarniMatheusBBarni
1

to-prd

Generate a template-based PRD from conversation and repository context.

Community
Advanced
dividedbydividedby
1

software-design

Orchestrate multi-module software design sessions with domain modeling and TDD-ready issue generation.

Community
Advanced
ulises-jeremiasulises-jeremias
2

dots-workstation-development-workflow

Standardize the default development lifecycle for projects without a custom workflow.

Community
Advanced