Generate a GitHub-issue PRD from user interviews and repository exploration.
npx skills add https://github.com/whyte25/reusables --skill write-a-prd-whyte25
Please help me install this Agent Skill. Skill: write-a-prd Source: https://github.com/whyte25/reusables/tree/main/.agents/skills/write-a-prd Command: npx skills add https://github.com/whyte25/reusables --skill write-a-prd-whyte25
It helps you transform a rough idea or feature request into a well-structured PRD by aligning you with users through interviews, validating assumptions against the current codebase, and designing the modules needed for implementation.
Ask the skill to write a PRD for your feature by providing a long, detailed description of the problem you want to solve and any initial solution ideas.
High-intent search queries and answers about installing and using this skill.
You convert user interviews into a product requirements document by systematically questioning assumptions and decision paths until details are resolved, producing a clear problem and solution statement. This process ensures a shared understanding of the requirements.
The best way to write a PRD for a major module refactor is to explore the existing codebase to verify claims and design testable module-level interfaces. This approach clarifies implementation decisions and confirms exactly what needs to be tested.
Yes, you can generate a GitHub issue directly from a feature plan by structuring finalized requirements into an implementation-oriented submission. This issue includes user stories, testing decisions, and clear out-of-scope items.
To structure testing decisions within a PRD, break the work into major modules and explicitly confirm what you want tested for each interface. This ensures testing requirements are defined alongside implementation decisions.
Yes, repo exploration helps validate product requirements by checking the current codebase to understand what already exists before specifying changes. This prevents duplicate work and ensures new modules align with existing dependencies.
Out-of-scope items in a feature PRD should include functionalities and design paths intentionally excluded from the current implementation phase. Defining these boundaries prevents scope creep and sets clear expectations for developers.
trevorbyrumInterview users to define project scope, assumptions, and constraints.
kinncjAutomates GitHub Project V2 board management by adding issues and updating fields.
SwitchbackTechAnalyze a codebase to produce a structured module-caller map.
luokai25Extract key information from arXiv papers and produce concise summaries.
