Synthesize conversation and codebase context into a PRD and publish it to the issue tracker.
npx skills add https://github.com/kos3nz/dotfiles --skill to-prd-kos3nz
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/kos3nz/dotfiles/tree/main/.config/agents/skills/to-prd Command: npx skills add https://github.com/kos3nz/dotfiles --skill to-prd-kos3nz
Turn the current conversation context into a PRD and publish it to the project issue tracker, enabling rapid alignment and planning without extra interviews.
Provide a PRD derived from the current context and publish it to the project issue tracker.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from conversation context, this Skill synthesizes your ongoing discussions and codebase understanding into a production-ready document. It automatically extracts scope, goals, success criteria, and risks without requiring further user interviews.
Yes, you can automatically publish a product requirements document directly to your project issue tracker. The generated PRD is formatted for publish-readiness and applies appropriate triage labels to ensure correct visibility and prioritization.
A PRD generated from project discussions includes major modules, user stories, acceptance criteria, and high-level implementation decisions. It synthesizes repository context to provide a complete document with scope, goals, success criteria, and identified risks.
Generating PRDs from codebase context works for existing project management workflows by outputting a tracker-ready format. It bridges planning and execution by applying triage labels directly within your project issue tracker for immediate team alignment.
The best way to turn planning discussions into user stories is to synthesize the conversation context into structured product documentation. This Skill automatically generates a set of user stories, acceptance criteria, and implementation decisions to guide next steps.
A limitation when synthesizing repository context into a PRD is that it relies solely on current conversation and codebase understanding without initiating further user interviews. Complex, undocumented features may require supplementary manual context gathering.
phillip-hirschGenerate a Product Requirements Document from conversation and codebase context.
AncienttwoConvert Product Requirements Documents into sprint backlogs and track tasks.
robbytAnalyze conversation history to propose targeted CLAUDE.md memory file improvements.
josemariafsDecompose product requirements and architecture decisions into epics and user stories with acceptance criteria.
