scope-coach

Identify minimal viable scope and propose a plan to ship it.

5|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/JasonWarrenUK/goblin-mode --skill scope-coach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-coach
Source: https://github.com/JasonWarrenUK/goblin-mode/tree/main/skills/scope-coach
Command: npx skills add https://github.com/JasonWarrenUK/goblin-mode --skill scope-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope creep stalls progress by encouraging bloated feature requests and overly long design cycles.

Core Features & Use Cases

  • Pushes for minimal viable scope to deliver real value
  • Provides concrete criteria and patterns to shrink scope
  • Helps teams decide what to build first and what to defer

Quick Start

Identify the minimal viable scope for the current feature and propose a plan to ship it.

Frequently Asked Questions about scope-coach

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

FAQPage Schema
How do I prevent feature creep during product planning?

To prevent feature creep, you need a framework that applies concrete scope questions and reduction patterns to shrink overly complex requests down to a minimal viable scope. This approach forces decisions on what to defer.

What is the smallest viable scope for an MVP?

The smallest viable scope is the minimum feature set required to deliver real value. It is determined by applying specific decision criteria and reduction patterns to strip away nice-to-haves during the planning phase.

How do we break analysis paralysis when deciding what features to build first?

Breaking analysis paralysis requires applying concrete decision criteria to prioritize what delivers value. A structured framework pushes teams to identify the minimal viable scope and propose a plan to ship it immediately.

What criteria should I use to shrink scope and defer nice-to-have features?

Shrinking scope requires applying concrete decision criteria and reduction patterns to evaluate feature requests. This framework helps teams decide what to build first and what to defer by focusing strictly on value delivery.

Does this scope reduction framework work for stalled design cycles?

Yes, this scope reduction framework is designed to apply when complexity grows or design cycles stall. It counteracts bloated requests by pushing for the smallest viable feature that satisfies core requirements.

When should I not use minimal viable scope reduction patterns?

Scope reduction patterns are not suitable when a project requires comprehensive feature delivery rather than an MVP. If analysis paralysis is not the issue and all requested features are mandatory, shrinking scope will fail to satisfy requirements.