Guide PRD creation through user interviews, codebase analysis, and module design.
npx skills add https://github.com/Icekole/my-opencode --skill write-a-prd-icekole
Please help me install this Agent Skill. Skill: write-a-prd Source: https://github.com/Icekole/my-opencode/tree/main/skills/write-a-prd Command: npx skills add https://github.com/Icekole/my-opencode --skill write-a-prd-icekole
This Skill addresses the challenge of creating a comprehensive Product Requirements Document (PRD) by guiding users through a structured process of user interviews, codebase exploration, and module design.
Use the write-a-prd skill to create a PRD for a new feature by following the structured interview and analysis process.
High-intent search queries and answers about installing and using this skill.
To create a PRD for a new feature, this skill guides you through structured interviews to define problem statements and solution ideas, analyzes your codebase to verify current state, and sketches module designs before submitting the document as a GitHub issue.
Structuring a product requirements document involves applying a predefined template after validating user assertions through codebase exploration. This process aligns feature requirements with actual module designs, ensuring technical feasibility before PRD creation.
Yes, structured interviews facilitate detailed problem and solution discussions to gather feature requirements. The resulting PRD is then formatted using a predefined template and submitted directly as a GitHub issue for development tracking.
Yes, user input on problem statements, solution ideas, and feature requirements is required. This input drives the structured interview process and subsequent codebase analysis to accurately outline necessary modules for implementation.
Codebase exploration inspects the current codebase state to verify user assertions made during interviews. This validation ensures that the sketched module designs accurately reflect existing technical constraints and implementation realities.
Using a predefined template for PRD creation standardizes the output format but requires complete user input regarding problem statements and feature requirements. The final GitHub issue submission relies heavily on the accuracy of the prior codebase analysis.
apocohqGenerate a structured PRD as a GitHub issue from stakeholder interviews and repo exploration.
chiruu12Convert conversation context into a PRD and submit it as a GitHub issue.
musher-devValidate architectural sketch assumptions against an existing codebase.
wiggitywhitneyGenerate a GitHub issue and milestone-structured PRD file.
