What problem does it solve? Product initiatives often arrive as oversized wishlists that mix v1 requirements with future-phase ideas, causing scope creep, unclear delivery boundaries, and PRDs that engineering cannot execute against. This Skill reduces a broad initiative into a realistic release scope with an explicit cut line. ## Core Features & Use Cases - Capability Inventory and Grouping: Extracts every capability mentioned in the input and groups them into logical blocks around the main user journey. - Four-Tier Scope Classification: Sorts items into must-have for v1, should-have if capacity allows, move to later phase, and explicitly out of scope, using prioritization rules based on user outcomes, trust, dependencies, and operational viability. - Structured Scope Memo: Produces a scope slicing memo in Russian covering release logic, technical/data/product/operational dependencies, scope creep risks, and a ready-to-paste PRD scope statement. - Use Case: A product manager has a draft PRD for a marketplace platform that bundles payments, recommendations, analytics, and loyalty programs. The Skill identifies the smallest coherent buyer journey, keeps payments and trust features in v1, defers recommendations and loyalty to later phases, and outputs a PRD-ready scope section. ## Quick Start Use the prd-scope-slicer skill to analyze my draft PRD and define what belongs in v1 versus later phases.