prd-doc-writer

Write PRDs and requirement documents with phased confirmation and visual diagrams.

Updated Feb 17, 2026

Search Tags:#documentation #mermaid #requirements gathering #user stories #prd #product requirements #ascii art

Ready to run

npx skills add https://github.com/Gatsbyhateyou/gatsby-website --skill prd-doc-writer-gatsbyhateyou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-doc-writer
Source: https://github.com/Gatsbyhateyou/gatsby-website/tree/main/.cursor/skills/prd-doc-writer
Command: npx skills add https://github.com/Gatsbyhateyou/gatsby-website --skill prd-doc-writer-gatsbyhateyou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation and iteration of Product Requirement Documents (PRDs) and other requirement specifications by employing a structured, story-driven approach. It aims to reduce ambiguity through visual aids like ASCII wireframes and Mermaid diagrams.

Core Features & Use Cases

Story-Driven Development: Breaks down requirements into self-contained user stories.
Phased Confirmation: Ensures consensus at each stage of the documentation process (framework, individual stories, final output).
Visual Aids: Utilizes ASCII for UI mockups and Mermaid for process/state/sequence diagrams to enhance clarity.
Use Case: When you need to document a new feature, this Skill will guide you through defining the user journey, detailing individual user stories with acceptance criteria, and visualizing the user interface and workflows before generating the final PRD.

Quick Start

Use the prd-doc-writer skill to help me write a PRD for a new user authentication feature.

Frequently Asked Questions about prd-doc-writer

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

FAQPage Schema

How do I write a PRD with clear user stories and acceptance criteria?▼

To write a PRD with clear user stories, use a story-driven, phased confirmation methodology that breaks down requirements into self-contained stories. This approach ensures consensus at each stage, detailing individual user stories with specific acceptance criteria before generating the final document.

How do you use Mermaid diagrams and ASCII wireframes to reduce PRD ambiguity?▼

Mermaid diagrams and ASCII wireframes reduce PRD ambiguity by visually mapping process flows, state sequences, and UI mockups. Integrating these visual aids directly into the requirement document clarifies complex user journeys and interface layouts for all stakeholders.

What is the step-by-step process for documenting product requirements iteratively?▼

The step-by-step process for documenting product requirements involves a structured three-step confirmation flow: defining the core business framework, detailing individual user stories, and generating the final output. This iterative methodology ensures stakeholder alignment at every phase.

Can I use this method to document a new feature without prior design assets?▼

Yes, you can document a new feature without prior design assets by utilizing ASCII art to create basic UI wireframes and Mermaid syntax for workflow diagrams. This allows you to visualize the user interface and process flows directly within the text-based PRD.

What is the best way to structure a product requirement document for a complex user journey?▼

The best way to structure a product requirement document for a complex user journey is a story-driven approach that isolates individual interactions. Validating the core business flow first, then expanding into granular user stories, minimizes structural ambiguity and maintains focus.