Generate a PRD from product discussion context and publish it to the issue tracker.
npx skills add https://github.com/Flowm/dotfiles --skill to-prd-flowm
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/to-prd Command: npx skills add https://github.com/Flowm/dotfiles --skill to-prd-flowm
This Skill eliminates the tedious, error-prone work of manually drafting Product Requirement Documents (PRDs) after product discussions, ensuring all agreed-upon details from the conversation are captured accurately without extra follow-up interviews.
Use the to-prd skill to turn our recent conversation about the new notification system into a published PRD on the project issue tracker.
High-intent search queries and answers about installing and using this skill.
Generate a PRD from a product discussion without stakeholder interviews by synthesizing existing chat context and codebase understanding into a complete document automatically. This eliminates manual drafting and prevents detail loss by compiling agreed-upon scope directly from the conversation.
Publish a generated PRD to your project issue tracker automatically by applying the skill to compile conversation context and push the document directly to the tracker. It applies a pre-configured ready-for-agent triage label to streamline downstream agent workflows.
Automatically generated PRDs respect project-specific architectural decision records, domain vocabulary, and existing code seams to ensure alignment. The synthesized document matches your project standards by analyzing the existing codebase context alongside the conversation.
Automating requirement drafting after finalizing feature scope is done by synthesizing the conversation context into a structured PRD. This approach captures all agreed-upon details accurately without extra follow-up interviews and publishes directly to your issue tracker.
Conversation synthesis for PRD generation requires no external dependencies or components. It operates independently to compile existing product discussion context and codebase understanding into a complete document for publishing.
ian-pascoeConvert conversation and codebase context into a structured PRD.
oxieBreak down implementation plans into 20-30 testable tasks with acceptance criteria.
arxxyrConvert conversation context and codebase understanding into a Product Requirements Document and publish it to the issue tracker.
AcendWayConvert conversation context into a structured PRD for GitHub issue submission.
