write-prd

Generates a structured Product Requirements Document with RICE scoring and approval workflow.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill write-prd-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/write-prd
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill write-prd-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document from scratch is time-consuming and often produces vague goals, unprioritized features, and unclear MVP boundaries. This Skill dispatches a product owner agent to produce a complete, industry-standard PRD with measurable success metrics and explicit scope. ## Core Features & Use Cases - Structured PRD Generation: Produces a 14-section PRD covering problem statement, personas, RICE-scored features, MVP scope, competitive analysis, risks, and launch criteria. - Duplicate Detection: Searches existing PRD/BRD/ADR docs and the Kanban board before writing, so it never silently overwrites an existing PRD. - Quality Gate & Approval Flow: Validates the draft against a checklist (RICE scores, measurable metrics, explicit MVP boundary) and requires explicit stakeholder approval before downstream agents act. - Use Case: You need a PRD for a new social login feature on an existing product. Provide the business driver, target users, and constraints, and receive a complete draft PRD saved to docs/artifacts/prd/ ready for review. ## Quick Start Ask the assistant to write a PRD for your feature, providing the business driver, target users, core capabilities, and any constraints.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I write a PRD for a new product feature?▼

Provide the feature description, business driver, target users, core capabilities, platforms, and constraints. The skill dispatches a product owner agent that returns a complete 14-section PRD with RICE-scored features, success metrics, and an explicit MVP boundary.

What sections should a product requirements document include?▼

This PRD template includes executive summary, problem statement, goals and non-goals, personas, user stories, RICE-scored features, MVP scope, competitive analysis, success metrics, dependencies, risks, launch criteria, open questions, and a changelog.

How is RICE prioritization calculated for product features?▼

RICE equals Reach times Impact times Confidence divided by Effort in person-weeks. Every feature in the PRD must carry a RICE score plus a business justification linking it to a goal or OKR, and is assigned a P0, P1, or P2 priority.

Does this skill overwrite an existing PRD for the same feature?▼

No. It first searches docs/artifacts/prd, brd, adr, and rfc directories plus the Kanban board for existing documents. If a PRD already exists, it asks whether to revise it or write a new version before proceeding.

When should I use a standalone PRD instead of a full planning chain?▼

Use a standalone PRD for a new feature on an existing product, an idea needing definition before committing to planning, or backfilling documentation for work in flight. Unlike the full new-product flow, it stops after one approved PRD without chaining into BRD or board setup.