write-prd

Authors validated Product Requirements Documents from a reusable template for downstream code planning.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill write-prd-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/write-prd
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill write-prd-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document that is complete, measurable, and ready for automated code planning is slow and error-prone; this Skill walks you through every required section, gates the draft against quality checks, and produces an approved PRD file. ## Core Features & Use Cases - Template-Guided Authoring: Loads the PRD template and walks through all ten required sections, from product identity to stakeholder approvals. - Quality Gate: Runs an ASAE validation pass checking for specific user segments, evidence-backed problem statements, measurable goals, and explicit non-goals. - Orchestrated and Standalone Modes: Integrates with /ideate-to-d2r-ready and /dare-to-rise-code-plan, supports remediation of single sections, and can emit a portable prompt for use in other LLM threads. - Use Case: You have an app idea and need a PRD before running an automated code-planning workflow; invoke this Skill to produce a versioned, approved PRD saved to your project's planning directory. ## Quick Start Ask the assistant to write a PRD for your project using the write-prd skill, providing the project name and filename prefix.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I write a product requirements document with Claude?

Invoke the write-prd skill with your project name and filename prefix. It loads the PRD template, walks you through each required section, validates the draft with an ASAE gate, and saves the approved file to your planning directory.

What sections should a PRD template include?

This template requires ten sections: product identity, users and problem, goals, user journeys, success criteria, constraints, assumptions, open questions, out of scope, and stakeholder approvals. Optional sections can be marked NA with a one-line justification.

Can I use this PRD skill standalone without the orchestrator?

Yes, standalone mode is the default. It runs a lightweight readiness check on five interrogation questions first, and recommends /ideate-to-d2r-ready if your answers are underdeveloped.

Can I generate a PRD prompt for a different LLM or thread?

Yes, portable prompt mode inlines the full template, your project context, filename conventions, and validation checklist into a single copyable prompt that works in any capable LLM without file access.

What are common PRD writing mistakes to avoid?

The anti-patterns reference covers vague user segments, intuition-only problem statements, unmeasurable goals, solutioning inside problem statements, and scope creep via vague criteria. The skill requires reading it before authoring.