write-a-prd

Convert client briefs into structured markdown PRDs for .NET projects.

Updated Jan 9, 2026

Search Tags:#project management #software development #structured writing #PRD generation #client communication

Ready to run

npx skills add https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards --skill write-a-prd-leesanderson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards/tree/main/.claude/skills/write-a-prd
Command: npx skills add https://github.com/LeeSanderson/OpinionatedDotNetCodingStandards --skill write-a-prd-leesanderson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users transform client briefs into a structured Product Requirements Document (PRD), streamlining project understanding and communication.

Core Features & Use Cases

Generate PRD: Turn client requests into a structured PRD in markdown format.
Project Context: Understands .NET solutions and the various layers involved in implementing features.
Process Workflow: Guides through a step-by-step process, including user interviews, module sketching, and writing the PRD with detailed sections such as Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes.

Quick Start

Invoke the write-a-prd skill and follow the prompts to create a PRD for your new project feature.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema

How do I generate a PRD from a client brief for software development?▼

To generate a PRD from a client brief, you need to convert the initial request into a structured markdown document. This process defines user stories, implementation decisions, and testing strategies to ensure comprehensive feature communication.

What is the best way to structure a Product Requirements Document for .NET project development?▼

The best way to structure a PRD for .NET project development is using structured markdown that outlines problem statements, solutions, user stories, and testing decisions. This format clarifies the various .NET solution layers required for implementing features.

What sections should be included when writing a PRD for a new project feature?▼

Writing a PRD for a new project feature should include specific sections: Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. This ensures complete project understanding and structured communication.

Can I use structured markdown to define implementation and testing decisions for client communication?▼

Yes, you can use structured markdown to define implementation and testing decisions for client communication. This approach transforms brief client requests into detailed planning documents, facilitating a step-by-step workflow from user interviews to module sketching.

Does a PRD generation process help with .NET solution layers and module sketching?▼

A PRD generation process directly helps with .NET solution layers and module sketching by guiding the workflow step-by-step. It translates client briefs into detailed requirements, ensuring all architectural layers involved in implementing features are properly planned.

When do I need a structured PRD for project management instead of a basic client brief?▼

You need a structured PRD for project management instead of a basic client brief when you must define detailed user stories, implementation decisions, and testing strategies. A structured document streamlines project understanding and comprehensive feature communication.