scoping-cutting

Installation
Summary

Help teams scope projects and cut features using frameworks from 15 product leaders.

  • Teaches appetite-based planning: set fixed time budgets and vary scope instead of extending deadlines
  • Covers eight core principles including MVP as validation tool, aggressive feature cutting, and the "build the scooter, not the axle" approach to end-to-end value
  • Provides Wizard of Oz testing guidance to validate hypotheses manually before engineering investment
  • Includes diagnostic questions and common mistakes to flag during scoping conversations
SKILL.md

Scoping & Cutting

Help the user scope projects and cut features effectively using frameworks from 15 product leaders.

How to Help

When the user asks for help with scoping:

  1. Understand the hypothesis - Ask what they're trying to learn or validate
  2. Identify the appetite - Determine how much time/resources they're willing to invest
  3. Find the essential core - Help them identify what must be present for the first version
  4. Design for learning - Ensure the scope enables fast feedback, not just fast shipping

Core Principles

Use appetite, not estimates

Ryan Singer: "We're going to go the other way around and we're going to say, what is the maximum amount of time we're willing to go before we actually finish something?" Set a fixed time budget (appetite) and design a version of the solution that fits within it. Vary scope, not deadlines.

MVP is a validation tool

Related skills
Installs
1.1K
GitHub Stars
879
First Seen
Jan 29, 2026