prd-writer

Write a full Russian product requirements document from discovery briefs and scope notes.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill prd-writer-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/prd-writer
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill prd-writer-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning rough discovery briefs, scope memos, or strategy notes into a structured, development-ready PRD is time-consuming and often produces ambiguous documents. This Skill generates a complete, professional PRD in Russian with explicit scope, testable requirements, metrics, risks, and rollout logic. ## Core Features & Use Cases - Canonical 17-section PRD structure: Covers executive summary, problem statement, users and roles, in/out of scope, workflows, functional and non-functional requirements, data and analytics, dependencies, risks, success metrics, rollout, and open questions. - Special handling rules: Adds operator queues, audit trails, and escalation flows for operator-assisted products; trust, access control, and abuse prevention for trust-sensitive products; states and transitions for workflow-heavy products. - Use Case: Provide a discovery brief for a new CRM module, and receive a complete Russian PRD with release scope, user journeys, testable requirements, and launch criteria ready for engineering, design, and QA review. ## Quick Start Use the prd-writer skill to write a complete Russian PRD from my discovery brief for the new marketplace onboarding flow.

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 PRD from a discovery brief?

Provide the discovery brief, scope memo, or strategy note as input and ask for a PRD. The skill normalizes the input into a release-level scope and produces a full document with problem statement, requirements, metrics, and rollout plan.

What sections should a product requirements document include?

This skill uses a 17-section structure: executive summary, problem statement, goals, users, in-scope and out-of-scope, current and future workflows, functional and non-functional requirements, data and analytics, dependencies, risks, success metrics, rollout, open questions, and appendix.

Can I write a PRD in Russian for a CRM or marketplace product?

Yes, the skill writes the entire PRD in Russian and explicitly supports CRM systems, marketplaces, SaaS products, internal tools, bots, and operator-assisted software. It adapts sections for trust-sensitive and workflow-heavy products.

Does the PRD include non-functional requirements like security and privacy?

Yes, the non-functional requirements section covers performance, reliability, security, privacy, auditability, explainability, and localization when relevant. Only categories applicable to the product are included.

When should I not use a full PRD structure?

A full PRD is excessive for tiny features or bug fixes that need only a short ticket. This skill targets release-level initiatives; for small changes, a lightweight task description is usually sufficient.