scoping-cutting

What problem does it solve?

This Skill helps teams define and commit to a realistic, ship-able scope within a fixed time budget, preventing scope creep and ensuring meaningful delivery.

Core Features & Use Cases

• Appetite-Based Scoping: Define a Minimum Lovable Slice (MLS) that fits a specific timebox (e.g., 2-6 weeks).
• Cut List Generation: Identify and justify scope items to cut or defer, with clear trade-offs.
• Hypothesis-Driven MVP: Frame Minimum Viable Products (MVPs) as tests for specific hypotheses, not just smaller feature sets.
• Scope-Change Guardrails: Establish clear rules for managing scope changes to prevent creep.
• Use Case: A product team has 4 weeks to deliver a new feature. They use this Skill to define the core user journey, cut non-essential elements, and create a plan to validate the feature's value quickly, ensuring they ship a valuable slice on time.

Quick Start

Use the scoping-cutting skill to define a minimum lovable slice for our new user onboarding flow with a 4-week appetite.