Convert conversation and codebase context into a structured PRD.
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill to-prd-ian-pascoe
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/to-prd Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill to-prd-ian-pascoe
This Skill turns an existing conversation and repo context into a structured product requirements document, helping teams move from discussion to an actionable plan without rehashing the same questions.
It synthesizes the current context into a PRD with a clear problem statement, solution, user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. It is especially useful when a product manager or engineer already has enough context to write requirements and wants a polished document ready for an issue tracker. It also supports consistent terminology and scope framing so the resulting PRD is easier for agents and teammates to use downstream.
Ask the skill to convert the current conversation into a PRD and publish it to the project issue tracker.
High-intent search queries and answers about installing and using this skill.
You can convert an existing conversation and codebase context into a structured PRD by synthesizing the discussion into a problem statement, user stories, and implementation decisions. This skips the need for additional interviews and makes the document ready for issue tracking.
Synthesizing feature requirements for issue tracking involves applying consistent repository glossary terms and architectural decisions to your conversation context. This frames the scope clearly and produces a structured PRD ready for agent handoff and issue tracker publication.
No, this PRD generation approach does not require interviewing the user. It relies entirely on existing conversation and codebase context to synthesize requirements, allowing you to move directly to an actionable plan without rehashing questions.
Yes, you can publish a PRD directly to your project issue tracker. The synthesized document includes structured sections for out-of-scope items and testing decisions, making it immediately actionable for product planning and ready-for-agent handoff workflows.
To ensure consistent terminology when generating requirements, you apply repository glossary terms and architectural decisions during the synthesis process. This maintains scope framing and produces a PRD that is easier for agents and teammates to use downstream.
yamcodesGenerate a PRD from conversation context and publish it to the issue tracker.
FlowmGenerate a PRD from product discussion context and publish it to the issue tracker.
huangzidaConvert conversation context into a glossary-aligned PRD for the issue tracker.
mmartinsolivConvert conversation and repository context into a publishable product requirements document.
