skills.rest
rickmanelius
rickmaneliusCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sys:high-medium-low

Define LOW, MEDIUM, and HIGH scope tiers with time and cost estimates.

3|Updated Mar 31, 2026
Search Tags:#scoping#prioritization#mvp#roadmapping#cost-estimation#product-strategy#value-assessment
One-click install
npx skills add https://github.com/rickmanelius/skills --skill sys-high-medium-low
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sys:high-medium-low
Source: https://github.com/rickmanelius/skills/tree/main/plugins/save-your-startup/skills/sys-high-medium-low
Command: npx skills add https://github.com/rickmanelius/skills --skill sys-high-medium-low

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams scope features at the wrong fidelity and over-invest in work that delivers little incremental value; this Skill forces you to define LOW, MEDIUM, and HIGH options so you build the minimum that proves value and avoid over-engineering.

Core Features & Use Cases

  • Three-tier scoping: Clearly defined LOW (minimal proof of concept), MEDIUM (best balance of value and cost), and HIGH (dream vision) deliverables.
  • Value-to-cost comparison: Side-by-side assessment of time, cost, risk, and expected learning for each tier to reveal where effort pays off.
  • Decision output: Time and cost estimates, the recommended starting tier, and escalation triggers for when to invest more.
  • Use Case: Scope an e-commerce checkout into a PayPal landing page LOW, a single-merchant integrated MEDIUM, and a full ERP-integrated HIGH to decide where to start.

Quick Start

Scope the feature you are building into LOW, MEDIUM, and HIGH, estimate time and cost for each tier, and recommend which tier to build first.

Frequently Asked Questions about sys:high-medium-low

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

FAQPage Schema
How do I define multiple scope tiers for a product feature to avoid over-engineering?▼

Defining scope tiers involves creating LOW, MEDIUM, and HIGH options for a product feature to compare value-to-cost tradeoffs. This method forces teams to estimate time, cost, and risk for each tier, recommending a starting point that proves value with minimal investment.

What is the best way to compare MVP scope options during roadmapping?▼

Comparing MVP scope options requires a three-tier scoping approach that evaluates minimal, balanced, and dream vision deliverables side-by-side. This reveals expected learning and cost estimation for each tier, helping teams decide what to build first without over-investing.

How do I estimate cost and effort for different project scopes?▼

Estimating cost and effort for project scopes requires breaking features into LOW, MEDIUM, and HIGH tiers. This generates specific deliverables with side-by-side time, cost, and risk assessments for each option to reveal where effort pays off.

Can I use three-tier scoping for internal initiatives and experiments?▼

Three-tier scoping applies directly to internal initiatives and experiments where teams must choose what to build first. It defines specific deliverables for each tier and establishes escalation triggers indicating when to invest more resources.

When should I escalate from a minimal proof of concept to a higher scope?▼

You should escalate from a minimal proof of concept to a higher scope based on predefined escalation triggers generated during the initial value assessment. These triggers indicate when incremental investment in MEDIUM or HIGH tiers delivers justified value.

Related Skills

Explore More Product & Management Skills→
kevinlinkevinlin
14

feature-spec

Generate a structured PRD with problem statements, goals, user stories, and acceptance criteria.

Community
Advanced
samhvw8samhvw8
14

planning-methodology

Produce detailed technical implementation plans with phased documents and actionable outputs.

Community
Basic
BertCalmBertCalm

session-economist

Monitor AI model usage and estimate session costs.

Community
Intermediate
calvyntwhcalvyntwh

pareto-principle

Prioritize tasks and features using the 80/20 rule with Value and Effort estimates.

Community
Intermediate