skills.rest
monlor
monlorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-prd

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

1|Updated Aug 16, 2023
Search Tags:#project management#issue tracker#PRD#codebase analysis#product requirements
One-click install
npx skills add https://github.com/monlor/dotfiles --skill to-prd-monlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/monlor/dotfiles/tree/main/config/ai/agents/skills/to-prd
Command: npx skills add https://github.com/monlor/dotfiles --skill to-prd-monlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill facilitates the transformation of conversation context into a Product Requirement Document (PRD) and automates the process of publishing it to a project's issue tracker, streamlining the creation of formal product requirements.

Core Features & Use Cases

  • Context-to-PRD Synthesis: Takes existing conversation context and codebase understanding to generate a PRD.
  • Automated Issue Tracker Integration: Publishes the PRD to a specified project issue tracker, with a label applied.
  • Use Case: A team discussing feature requests in a meeting can use this skill to capture those requirements, synthesize them into a PRD, and post it directly to the project repository.

Quick Start

Generate a PRD from the current conversation and publish it to the project issue tracker using the 'to-prd' skill.

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 an issue tracker?▼

To convert conversation context into a PRD, synthesize your discussion and codebase knowledge into a formal document, then publish it directly to a project issue tracker with applied triage labels.

What is the process for generating product requirements from a codebase?▼

Generating product requirements from a codebase involves analyzing existing code and domain glossaries, combining them with conversation context, and creating a structured PRD for the issue tracker.

Do I need a domain glossary to publish a PRD to my project repository?▼

Yes, creating a PRD requires access to the project's domain glossary and ADRs to accurately synthesize codebase knowledge and apply specific triage labels during issue tracker publication.

How do I apply triage labels when publishing product requirements to an issue tracker?▼

Publishing product requirements to an issue tracker applies specific triage labels automatically during the PRD creation process, streamlining project management and issue categorization.

Can I automate product requirement document creation from meeting discussions?▼

Yes, you can automate PRD creation from meeting discussions by capturing the conversation context, synthesizing it with codebase understanding, and publishing the formalized requirements to the issue tracker.

Related Skills

Explore More Software Engineering Skills→
JohnRobert-OlanoJohnRobert-Olano

to-prd

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

Community
Intermediate
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
rito528rito528
1

issue-triage

Parse GitHub issue content and apply status labels via the GitHub API.

Community
Intermediate
nkabbarankabbara

to-spec

Synthesize conversation logs into software product requirement documents.

Community
Advanced