scope-cutting

Included with Lifetime

$97 forever

Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.

General

What this skill does

Cut scope by flipping the question. Instead of "How long will this take?" ask "How much time is this problem WORTH?" Set the appetite first, then shape the solution to fit. This is Shape Up's core insight: fixed time, variable scope.

## Set the Appetite

Before touching scope, declare the time budget:

- **Small batch:** 1-2 weeks for 1-2 people
- **Big batch:** 6 weeks max for a small team

If a project takes more than 6 weeks (or 3 weeks for 1-3 people per Linear's method), it's too big. Break it down or walk away.

The appetite is NOT an estimate. An estimate says "this will take X." An appetite says "this is WORTH X." If the shaped solution doesn't fit the appetite, cut scope until it does — or kill the project.

## Scope Hammering

For every item in the spec, ask these questions in order:

1. **Must-have or nice-to-have?** If the feature ships without it and users still get value, it's nice-to-have. Cut it.
2. **Shippable without it?** Can you deploy a working version that doesn't include this? If yes, cut it from v1.
3. **Edge case or core path?** If fewer than 20% of users will encounter this scenario, defer it.
4. **Compare to baseline.** The baseline is NO feature — not the ideal version. "Is this better than nothing?" always wins over "Is this as good as it could be?"

## Shape the Solution Down

When scope is still too big after hammering:

- **Cut breadth, not quality.** Support 1 auth provider well instead of 3 badly. Handle the happy path completely instead of covering every error state.
- **Remove entire surfaces.** Kill the settings page. Remove the dashboard. Ship with sensible defaults instead of configurability.
- **Time-bound the edge cases.** "We'll handle CSV import of up to 1,000 rows. Above that, they email us." Solve it manually until scale demands automation.
- **Ask: "What's the simplest version a customer would thank us for?"** That's your scope.

## Circuit Breaker (Shape Up)

If it doesn't ship in one cycle, it's cancelled by default. No automatic rollover. The team must re-pitch for another cycle. This prevents zombie projects that drag on forever.

## Guidelines

- CRITICAL: NEVER cut quality — cut BREADTH. A polished feature that does one thing > a buggy feature that does five.
- NEVER estimate. Set appetite. "This is worth 2 weeks" not "This will take 2 weeks."
- NEVER let v1 have more than 5 must-haves. If it does, you haven't scoped hard enough.
- ALWAYS compare to baseline (no feature at all), not to the ideal implementation.
- ALWAYS ask "What can we ship in [appetite]?" not "How long until we ship everything?"
- NEVER carry work over automatically. Unfinished work must be re-pitched.

---

*Built on Shape Up (Basecamp) and the Linear Method. Skills from [productskills](https://github.com/assimovt/productskills).*

Files: 1

Size: 3.0 KB

Complexity: 7/100

Category: General

Source: https://github.com/assimovt/productskills/tree/main/skills/scope-cutting

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts