prd-scope-slicer

Cut broad product initiatives into a realistic v1 release scope and phased roadmap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about prd-scope-slicer

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

FAQPage Schema
How do I cut scope for a v1 product release?

Identify the primary user journey, then keep only capabilities required for that outcome, trust and safety, operational viability, or hard dependencies. Move experience improvements, personalization, and edge cases to later phases and mark unrelated items explicitly out of scope.

How to decide what belongs in v1 versus a later phase?

Keep an item in v1 if it unlocks the core workflow, is required for security or auditability, or blocks other v1 items. Defer items that add automation, growth features, or complexity without reducing core launch risk.

When should I use scope slicing before writing a PRD?

Use it when the initiative is too broad, the draft PRD mixes v1 and phase 2, the scope reads like a wishlist, or engineering needs a clearer delivery boundary. It works both before PRD writing and during PRD refinement.

What output does the PRD scope slicing process produce?

It produces a scope slicing memo in Russian with the initiative boundary, full capability inventory, four-tier release cut, release logic, key dependencies, scope creep risks, and a ready-to-paste PRD scope statement.

Does scope slicing require external data or integrations?

No. The Skill is universal and works purely from the input materials you provide, such as a product idea, roadmap block, or draft PRD. It requires no connectors, APIs, or external data sources.