skills.rest
orqesa
orqesaOFFICIAL
Explore all skills by this author →
GitHub

prd_writer

Generate comprehensive Product Requirement Documents with problem definition, scope, user stories, and analytics tracking.

Updated Aug 27, 2026
Search Tags:#documentation#feature development#requirements#product management#prd#stakeholder alignment
One-click install
npx skills add https://github.com/orqesa/orqesa-roles --skill prd-writer-orqesa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd_writer
Source: https://github.com/orqesa/orqesa-roles/tree/main/roles/cpo/skills/prd-writer
Command: npx skills add https://github.com/orqesa/orqesa-roles --skill prd-writer-orqesa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps create clear, actionable Product Requirement Documents (PRDs) that ensure alignment between engineering, design, and business teams on product development.

Core Features & Use Cases

  • Problem Clarification: Defines the customer problem and its validation.
  • Outcome Definition: Establishes measurable success metrics.
  • Scope Management: Clearly defines what is in and out of scope for development.
  • User Story & Acceptance Criteria: Documents requirements in a structured format.
  • Analytics & Rollout Planning: Specifies data tracking and deployment strategies.
  • Use Case: When a new feature is approved, use this Skill to generate a comprehensive PRD that guides the development team and aligns stakeholders before design or engineering begins.

Quick Start

Use the prd_writer skill to draft a product requirement document for a new user authentication feature.

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 product requirement document that aligns stakeholders?▼

To write a product requirement document that aligns stakeholders, define the customer problem, establish measurable success metrics, and clearly outline the development scope to guide engineering and design teams.

What should be included in a PRD for new feature development?▼

A PRD for new feature development should include problem clarification, measurable outcome definitions, scope management, user stories, acceptance criteria, analytics tracking, and rollout planning strategies.

How do I define acceptance criteria and user stories for product management?▼

Define acceptance criteria and user stories for product management by documenting feature requirements in a structured format that establishes clear, unambiguous development boundaries and validation conditions for engineering teams.

When do I need a PRD for feature development?▼

You need a PRD for feature development when a new feature is approved and you must align business, design, and engineering teams on product initiatives before actual design or engineering work begins.

Does this PRD writer handle scope management and rollout planning?▼

Yes, this PRD writer handles scope management by defining what is in and out of development scope, and manages rollout planning by specifying data tracking requirements and deployment strategies.

Related Skills

Explore More Product & Management Skills→
AWS-EducateAWS-Educate

product-marketing-context

Create and update product marketing context documents at `.claude/product-marketing-context.md`.

Official
Intermediate
shwilliamsonshwilliamson

user-stories

Write user stories with acceptance criteria and INVEST guidelines.

Community
Basic
Razmik-KutinavaRazmik-Kutinava

Product Roadmap Generator

Generate product roadmaps organized by strategic themes and business outcomes.

Community
Advanced
lluppesmslluppesms

breakdown-feature-prd

Generate structured Markdown PRDs from Epic feature descriptions.

Community
Intermediate