write-a-prd

Name: write-a-prd
Availability: InStock
Author: icekole

Guide PRD creation through user interviews, codebase analysis, and module design.

Updated Mar 19, 2026

Search Tags:#codebase analysis #module design #structured interview #PRD creation #GitHub issue submission

Ready to run

npx skills add https://github.com/Icekole/my-opencode --skill write-a-prd-icekole

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

User Interview Guidance: Facilitates detailed problem and solution discussions with users.
Codebase Exploration: Verifies user assertions and understands the current codebase state.
Module Design Sketching: Assists in outlining necessary modules for feature implementation.
PRD Template Application: Uses a predefined template to write and submit a PRD as a GitHub issue.
Use Case: Ideal for product managers or developers who need to plan a new feature or document existing requirements.

Quick Start

Use the write-a-prd skill to create a PRD for a new feature by following the structured interview and analysis process.

Frequently Asked Questions about write-a-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a PRD for a new feature in an existing codebase?▼

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.

What is the best way to structure a product requirements document using codebase analysis?▼

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.

Can I use structured interviews to plan a new feature and submit it to GitHub?▼

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.

Do I need to provide problem statements before starting the PRD creation process?▼

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.

How does codebase exploration verify user assertions during module design?▼

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.

What are the limitations of using a predefined template for PRD creation?▼

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.