From save-your-startup
Define three scope tiers for any project -- LOW (minimum proof of concept), HIGH (dream version), and MEDIUM (best balance of value and cost) -- to make smarter build decisions and avoid over-engineering.
npx claudepluginhub rickmanelius/skills --plugin save-your-startupThis skill uses the workspace's default tool permissions.
**From *Save Your Startup* by Rick Manelius (Chapter 10)**
Scopes MVPs by defining core hypotheses, triaging features with effort/impact scoring, outlining 2-week sprints, and setting success criteria. Activates on 'MVP' or scoping requests.
Turns ideas into buildable feature specs, project scopes, requirements, or MVP definitions. Guides quick workflows for AI builds and full scopes for planning and estimates.
Guides 4-step Shape Up process to shape work into pitches for betting. Supports established (fixed time, variable scope) and new product modes for cycle planning and PM coaching.
Share bugs, ideas, or general feedback.
From Save Your Startup by Rick Manelius (Chapter 10) Original framework by Rick Manelius
"Can you get 90% there for 10% -- or 1% or 0.1% -- of the cost?"
Founders and builders have a dangerous habit: they describe "done" at one fidelity level and then build at another. Someone says "we need e-commerce" and the team jumps to a six-month ERP integration when a PayPal button would have answered the real question in five minutes.
The problem is not ambition. The problem is skipping the question: what is the cheapest way to learn if this matters?
Here is the key insight:
"If I triple the time from one month to one quarter, do I triple the value? You probably won't."
Value and cost do not scale linearly. The first 10% of effort often delivers 80% of the value. This exercise forces you to see that clearly before you commit.
We will define three tiers of scope for your project, then compare the value-to-cost ratio at each level. By the end, you will know exactly where to start and why.
But first -- a bias check.
Before we scope anything, I need to ask:
Everyone gravitates toward one end of the spectrum. Knowing your default helps us compensate. If you always think big, we will spend extra time on LOW. If you always think small, we will push on HIGH.
Before we split into tiers, tell me what you are building. Do not filter or optimize yet.
I will ask you:
This gives us a starting point. Now we will stretch it in both directions.
The minimum proof of concept. Aim for a one-day to one-week build.
LOW is not "bad." LOW is "what is the cheapest, fastest way to test whether this idea has legs?"
I will ask you:
Example -- e-commerce LOW: "Five minutes. A PayPal button on a landing page. We learn if anyone will actually pay."
The dream version. The north star. One to two years, everything perfect.
HIGH is not the plan. HIGH is the vision -- what would this look like if time, money, and talent were unlimited?
I will ask you:
Example -- e-commerce HIGH: "A thousand hours. Full-blown commerce platform with inventory management, ERP integrations, subscription billing, recommendation engine, and multi-currency support."
Return to the middle. The best balance of value and cost.
Now that you can see both ends, MEDIUM becomes much clearer. It is not "half of HIGH." It is the version that delivers the most value per unit of effort.
I will ask you:
MEDIUM is where most teams should start building. But you can only define a good MEDIUM after you have honestly looked at both extremes.
What is the value-to-cost ratio at each tier?
Now we lay them side by side:
| Tier | Time | Cost | Value Delivered | Value per Unit of Cost |
|---|---|---|---|---|
| LOW | ? | ? | ? | ? |
| MEDIUM | ? | ? | ? | ? |
| HIGH | ? | ? | ? | ? |
I will ask you:
Let's scope your project. Tell me:
I will walk you through each tier and push you to be honest about where the real value lives.
By the end, you will have: