Convert existing conversations into structured product requirements documents.
npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill to-prd-fabiendehopre
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/FabienDehopre/my-netatmo-24/tree/main/.agents/skills/to-prd Command: npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill to-prd-fabiendehopre
This Skill transforms existing conversation context and codebase understanding into a structured product requirements document without requiring additional user interviews.
Use the to-prd skill to create a PRD from the current conversation context and prepare it for the project issue tracker.
High-intent search queries and answers about installing and using this skill.
Product requirements documents generated from conversations synthesize user stories, implementation decisions, and testing plans. They format this information into a structured PRD with consistent formatting and triage metadata, preparing it directly for publication to an issue tracker.
Yes, generating user stories without discovery interviews is possible by converting existing conversation context into structured PRDs. The to-prd skill extracts requirements, architectural considerations, and testing plans directly from available project context.
To prepare a PRD for an issue tracker, apply project context and issue tracker conventions to generate a publishable PRD. This formats the document with consistent structure and appropriate triage metadata for direct integration into your planning workflow.
Creating a PRD from a conversation requires existing conversation context, codebase understanding, and access to project context and issue tracker conventions. This input allows the generation of a structured PRD with accurate scope boundaries and triage metadata.
A limitation of converting conversations into PRDs is that the output relies entirely on existing context, so missing information from unrecorded discussions will not be captured. It synthesizes available context rather than performing new requirement discovery to fill gaps.
yyopcGenerate a Product Requirements Document from conversation context and publish it to the issue tracker.
MatheusBBarniGenerate a template-based PRD from conversation and repository context.
anonymousminatiConvert conversation context into a structured PRD and publish it to the issue tracker.
cvillamarp-lgtmPlan and conduct discovery interviews to uncover customer needs.
