Convert conversation context into a PRD and publish it to the issue tracker.
npx skills add https://github.com/Rayzerrek/dotfiles --skill to-prd-rayzerrek
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/Rayzerrek/dotfiles/tree/main/.agents/skills/to-prd Command: npx skills add https://github.com/Rayzerrek/dotfiles --skill to-prd-rayzerrek
This Skill turns existing conversation context and repository understanding into a ready-to-publish product requirements document, so product work can move forward without starting from scratch.
Ask the skill to create a PRD from the current discussion and publish it to the project issue tracker.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document, the Skill synthesizes your current conversation context into a structured PRD and publishes it directly to your project issue tracker with appropriate triage labels.
Creating a PRD organizes context into problem, solution, user stories, implementation decisions, testing decisions, out of scope, and further notes to provide complete product requirements coverage.
Yes, you can create user stories and define a testing strategy without manual interviews because the Skill automatically synthesizes extensive user stories and testing decisions from current repository context.
Yes, a connected repository is required because the Skill relies on repository exploration and domain glossary alignment to accurately define module selection and feature scope for the PRD.
The best way to triage feature planning items is to apply needs-triage labeling during PRD publication, ensuring the generated product requirements are automatically categorized correctly in the issue tracker.
PRD generation leaves features out of scope to establish clear boundaries, applying module selection and scope definition logic to ensure only relevant product requirements are published to the issue tracker.
dividedbyOrchestrate multi-module software design sessions with domain modeling and TDD-ready issue generation.
vm0-aiConvert conversation context into structured GitHub issues with labels.
samuel-morrisseyGenerate a Product Requirements Document from conversation context and publish it to the issue tracker.
mmartinsolivConvert conversation and repository context into a publishable product requirements document.
