skills.rest
xianmingyao
xianmingyaoCOMMUNITY
Explore all skills by this author →
GitHub

prd-writer

Draft strategy-first PRDs with YAML frontmatter and structured Markdown templates.

1|1|Updated Mar 18, 2026
Search Tags:#template#documentation#requirements#ai#strategy#prd#product-management
One-click install
npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill prd-writer-xianmingyao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/xianmingyao/openclaw-CaySon/tree/main/skills/prd-writer
Command: npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill prd-writer-xianmingyao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Drafting comprehensive PRDs that emphasize strategic rationale while avoiding feature laundry lists, helping teams align on goals and outcomes.

Core Features & Use Cases

  • Strategy-first PRDs that explain why a feature exists and how it maps to business goals.
  • Structured templates covering Background & Goals, Users & Scenarios, Solution, Strategy Design, Technical Dependencies, Risks & Fallback, and Milestones.
  • Use Case: turning raw ideas into structured requirement docs that justify decisions and guide implementation.

Quick Start

Create a strategy-first PRD for a new feature, including background, goals, user segments, and success metrics.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I write a strategy-first PRD that aligns stakeholders?▼

To write a strategy-first PRD, use a structured template covering Background, Goals, Users, Solution, Strategy Design, Dependencies, Risks, and Milestones to justify business impact and align teams on outcomes.

What is the difference between a strategy-first PRD and a feature proposal?▼

A strategy-first PRD emphasizes the "why" over the "how," justifying business impact and mapping features to goals, whereas a standard feature proposal often functions as a feature laundry list without strategic rationale.

How do I structure a product requirements document to avoid feature laundry lists?▼

Structure a product requirements document using templates that cover Background, Goals, User Segments, Solution, Strategy Design, Technical Dependencies, Risks, and Milestones to focus on strategic rationale and business goals.

Can I use AI strategy components in my PRD documentation?▼

Yes, you can incorporate AI strategy components into your PRD documentation through templates, adding them alongside optional references to support the structured Markdown body and YAML frontmatter.

When do I need a strategy rationale in my requirement docs?▼

You need a strategy rationale in requirement docs when turning raw ideas into structured proposals, ensuring the document justifies decisions, emphasizes business impact, and guides implementation effectively.

What are the limitations of using templates for product management documentation?▼

Templates for product management documentation focus on structured strategy-first sections like Background, Goals, and Milestones, which may not suit projects requiring open-ended formatting or detailed technical implementation specs.

Related Skills

Explore More Product & Management Skills→
henrybravohenrybravo

prd-generation

Generate structured Product Requirements Documents from stakeholder input and templates.

Community
Intermediate
9thLevelSoftware9thLevelSoftware
1

portfolio-manager

Aggregate project state files into a global portfolio registry with health metrics.

Community
Advanced
AskTinNguyenAskTinNguyen

prd-enterprise

Generate structured enterprise PRDs with executive summary, requirements, and risk sections.

Community
Advanced
vertivolatamvertivolatam
1

Feature-First Architecture

Organize Flutter code by business domain features with BLoC state management.

Official
Intermediate