write-a-prd

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

Generate a Product Requirements Document through guided problem and solution exploration.

Updated Nov 23, 2025

Search Tags:#documentation #software development #requirements #product management #feature planning #prd

Ready to run

npx skills add https://github.com/remiconnesson/v0-video2md --skill write-a-prd-remiconnesson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/remiconnesson/v0-video2md/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/remiconnesson/v0-video2md --skill write-a-prd-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists in the creation of comprehensive Product Requirements Documents (PRDs) for new features, ensuring all aspects of a product are considered before development.

Core Features & Use Cases

Guided PRD Creation: Walks users through defining problems, solutions, user stories, and implementation details.
Codebase Exploration: Can analyze the existing repository to inform PRD decisions.
Use Case: A product manager needs to define a new feature for a software application. They use this Skill to systematically gather requirements, outline the scope, and document technical decisions, resulting in a well-structured PRD ready for the engineering team.

Quick Start

Use the write-a-prd skill to start drafting a PRD for a new user authentication system.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema

How do I write a PRD for a new software feature?▼

To draft a PRD for a new feature, you need to define the problem, explore solutions, create user stories, and specify implementation details. This Skill systematically walks you through these stages to generate a complete requirements document.

What should be included in product requirements documentation for software development?▼

Product requirements documentation should include problem definitions, proposed solutions, user stories, and testing decisions. This Skill generates a comprehensive PRD by guiding you through these exact structural components to ensure all product aspects are considered before development.

Can I generate a PRD by analyzing an existing codebase?▼

Yes, you can generate a PRD informed by an existing codebase. This Skill supports detailed repository analysis to help define the project scope and inform module design decisions directly within the product requirements document.

What is the best way to structure user stories in a feature planning document?▼

The best way to structure user stories in feature planning is to align them with defined problems and explored solutions. This Skill guides you through creating user stories as a core step of the PRD generation process to ensure technical scope is accurately captured.

Do I need technical knowledge to create requirements for a new user authentication system?▼

You need a clear problem definition to create requirements for a user authentication system, but the Skill guides the technical scoping. It helps you outline implementation and testing decisions even if you are primarily focused on product management.