write-a-prd

Convert vague feature ideas into structured product requirements documents.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/kvithayathil/agent-resources --skill write-a-prd-kvithayathil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/kvithayathil/agent-resources/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/kvithayathil/agent-resources --skill write-a-prd-kvithayathil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle to turn vague, unstructured feature ideas into clear, actionable product requirements that align with stakeholders, developers, and business goals, leading to miscommunication and wasted development effort.

Core Features & Use Cases

  • Guided User Interviews: Systematically clarify feature requirements and constraints through targeted questions to the user.
  • Codebase Exploration: Validate user assumptions by reviewing existing code and architecture to avoid redundant work.
  • Modular Implementation Planning: Identify deep, testable modules needed for the feature to ensure scalable, maintainable code.
  • Automated PRD Generation: Compile all gathered information into a standardized PRD and submit it directly as a GitHub issue for tracking. Use Case: If you have a rough idea for a new user notification feature, this skill walks you through refining requirements, checking existing code, designing modules, and outputs a ready-to-use PRD as a GitHub issue for your development team.

Quick Start

Use the write-a-prd skill to create a PRD for the new user notification feature I want to add to our app.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I turn a vague feature idea into a structured product requirements document?

Creating a structured product requirements document from a vague feature idea involves systematically clarifying requirements through user interviews, validating assumptions against existing code, and designing modular implementation plans to ensure alignment across stakeholders.

How do I generate a PRD formatted for submission as a GitHub issue?

You can generate a PRD for a GitHub issue by compiling gathered problem statements, user stories, and testing decisions into a standardized format ready for direct submission to your repository for development tracking.

What is the best way to validate feature assumptions against an existing codebase?

The best way to validate feature assumptions against an existing codebase is by exploring the current code and architecture to avoid redundant work, ensuring new modules integrate scalably and maintainably.

How do I plan modular implementation for a new feature?

To plan modular implementation for a new feature, you identify deep, testable modules required for the functionality, ensuring the resulting code architecture remains scalable and maintainable.

Does this PRD workflow require any specific dependencies or tools?

This PRD workflow does not require specific external dependencies, utilizing guided user interviews and codebase exploration to produce a standardized PRD formatted for GitHub issue tracking.