write-a-prd

Draft structured PRDs from interviews, repository analysis, and design decisions.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill write-a-prd-avoidthekitchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/avoidthekitchen/avilingo-v2/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill write-a-prd-avoidthekitchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured PRD from a free-form problem description by guiding user interviews, codebase exploration, and module design, then saving the result as a file.

Core Features & Use Cases

  • Interview-led planning: capture user needs, goals, and constraints through guided questioning.
  • Codebase-informed analysis: verify feasibility by inspecting modules, files, and patterns in the repository.
  • PRD templating and storage: generate a complete PRD document and persist it to a user-specified location or path.

Quick Start

Describe a problem in detail and specify where the PRD should be saved.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I draft a structured PRD from a free-form feature idea?

Drafting a structured PRD starts with guided user interviews to capture goals and constraints, then analyzes the codebase to verify feasibility before outlining design decisions and saving the final document.

What is the best way to write a PRD that aligns with existing codebase patterns?

Writing a PRD aligned with codebase patterns involves inspecting repository modules and files to verify feasibility, ensuring design decisions match current architecture before persisting the requirements document.

Can I generate a product requirements document for a system redesign and save it to a specific path?

Generating a product requirements document for a system redesign produces a formal PRD file that can be saved directly to a user-specified path or file location.

How does an interview-led PRD workflow capture project requirements?

An interview-led PRD workflow captures project requirements by guiding users through targeted questions about needs, goals, and constraints, transforming answers into structured design decisions.

What information do I need to provide to generate a PRD for a new feature?

To generate a PRD for a new feature, provide a detailed problem description and specify the desired output path where the finalized product requirements document should be saved.

Are guided interviews required to outline design decisions for feature improvements?

Guided interviews are used to outline design decisions for feature improvements, capturing necessary user needs and constraints to ensure the resulting PRD accurately reflects project feasibility.