prd-doc-writer

Writes PRD documents through staged user confirmations with ASCII wireframes and Mermaid diagrams.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/sliec/shared-files --skill prd-doc-writer-sliec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-doc-writer
Source: https://github.com/sliec/shared-files/tree/main/skills/prd-doc-writer
Command: npx skills add https://github.com/sliec/shared-files --skill prd-doc-writer-sliec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing a PRD alone often leads to ambiguous requirements, missing edge cases, and misaligned UI expectations between product managers and developers. This Skill turns PRD writing into a guided, confirmation-driven dialogue where every stage, story, and wireframe is explicitly approved before the final document is generated. ## Core Features & Use Cases - Three-Step Confirmation Workflow: Aligns on a user journey map first, confirms each user story individually, then requires an explicit final approval before generating the complete PRD. - Visual Requirement Alignment: Uses ASCII wireframes for UI layout consensus and Mermaid diagrams (flowcharts, state machines, sequence diagrams) to clarify dynamic behavior without technical implementation details. - Structured Output Template: Generates PRDs with value statements, business logic, exception handling, GIVEN-WHEN-THEN acceptance criteria, plus a PRD registry row for version tracking in the project repository. - Use Case: A product manager needs to specify a batch image-grading feature. The Skill walks them through journey mapping, per-story detail collection, wireframe review, and produces a developer-ready PRD with acceptance criteria covering both success and failure paths. ## Quick Start Ask the assistant to help you write a PRD for your feature, for example: help me write a PRD for a batch task creation page with image upload and answer validation.

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 user stories and acceptance criteria?

Start by defining a user journey map with logical stages, then detail each user story with value statements, business logic, and exception handling. Acceptance criteria use the GIVEN-WHEN-THEN format covering both success and failure scenarios.

What is the best way to align UI requirements with developers?

Use ASCII wireframes to draft page layouts showing element positions and hierarchy, then confirm them with stakeholders before finalizing. Pair wireframes with Mermaid flowcharts or state diagrams to describe dynamic behavior without implementation details.

When should I use Mermaid diagrams in a PRD?

A flowchart of the core user operation flow is required for every PRD. Add a state machine diagram when a clear state-transition object exists, such as orders or approvals, and a sequence diagram only when timing or concurrency affects user-visible outcomes.

Can this Skill generate a PRD without user confirmation?

No. The workflow strictly requires confirmation at three gates: journey map alignment, per-story single-point confirmation, and an explicit final generation approval. It never invents requirements the user has not stated.

How do I manage PRD versions across a project?

Maintain a PRD registry file such as docs/PRD_REGISTRY.md in the project repository, with one row per PRD pointing to its latest document path. Historical versions are tracked through Git rather than inside the registry itself.