prd-writing

Consolidates system constants, state schemas, and PRD section definitions into a single reference.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wlee075/chatbot --skill prd-writing-wlee075
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writing
Source: https://github.com/wlee075/chatbot/tree/main/skills/prd-writing
Command: npx skills add https://github.com/wlee075/chatbot --skill prd-writing-wlee075

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates system-wide constants, state fields, graph topology, and PRD section definitions into a single authoritative master reference to prevent duplication and inconsistency.

Core Features & Use Cases

  • Centralizes system constants, state schemas, graph topology, and PRD section definitions for the PRD chatbot.
  • Enables downstream skills to reference a single source of truth, ensuring consistent terminology, structure, and behavior across elicitation, drafting, and reflection.
  • Use Case: When multiple teams collaborate on a PRD, refer to this master to align sections, requirements, and evaluation rubrics.

Quick Start

Refer to this master reference to understand the PRD system's constants, state fields, graph topology, and the 13 PRD sections.

Frequently Asked Questions about prd-writing

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

FAQPage Schema
How do I standardize PRD sections across multiple collaborating teams?

To standardize PRD sections, this Skill consolidates 13 PRD section definitions and system-wide constants into a single authoritative master reference, ensuring consistent terminology and structure across all collaborating teams.

How do I maintain consistent state schemas during PRD elicitation and drafting?

To maintain consistent state schemas, this Skill centralizes state field definitions into a master reference that downstream workflows query during elicitation and drafting, preventing duplication and ensuring uniform data representation across the PRD system.

What is the best way to manage system constants in PRD development workflows?

The best way to manage system constants is referencing a centralized master reference that defines shared graph topology and PRD sections, preventing duplication and inconsistency across elicitation, drafting, and reflection phases.

Do I need a master reference to align PRD requirements and evaluation rubrics?

Yes, you need a master reference to align PRD requirements and evaluation rubrics, providing centralized constants and section definitions so multiple teams can collaborate without structural divergence or duplicated configuration.