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.