Generate a Product Requirements Document from conversation and codebase context.
npx skills add https://github.com/phillip-hirsch/dotfiles --skill to-prd-phillip-hirsch
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/phillip-hirsch/dotfiles/tree/main/.agents/skills/to-prd Command: npx skills add https://github.com/phillip-hirsch/dotfiles --skill to-prd-phillip-hirsch
This Skill synthesizes current conversation context and codebase understanding into a Product Requirements Document (PRD), enabling users to create and publish PRDs efficiently.
Run the to-prd skill to generate a PRD for the current project context.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from existing project context, use the to-prd Skill to analyze current conversation and codebase context, automatically synthesizing project domain and architecture understanding into a Product Requirements Document.
Yes, you can publish a PRD directly to your project issue tracker. The Skill automatically creates the document from current context and publishes it using a predefined triage label for immediate team review.
The best way to create a PRD without additional user interviews is to use contextual PRD creation, which synthesizes your current conversation and codebase understanding into a structured document based on the existing project state.
PRD generation works with your codebase architecture and project vocabulary by analyzing the current conversation context to ensure accurate document creation that reflects your specific project domain and technical terminology.
To create an accurate PRD, you need to provide sufficient context regarding your project domain, architecture, and vocabulary. The Skill requires this codebase understanding to synthesize conversation context into a precise Product Requirements Document.
A limitation of automatically generating a PRD from conversation context is that it relies entirely on existing codebase understanding and current dialogue, meaning incomplete project context or missing architectural details may result in an inaccurate requirements document.
flaviogragnolatiConvert conversation context and codebase understanding into a PRD and publish it to the issue tracker.
oxieBreak down implementation plans into 20-30 testable tasks with acceptance criteria.
ruskibeatsConvert conversation context into a structured PRD and publish it to the issue tracker.
christopher-bussGenerate a Product Requirements Document from conversation context and codebase understanding.
