scope-negotiate

Align stakeholder and product team scope decisions with MVP definition and trade-off matrices.

13|3|Updated Mar 27, 2026

Search Tags:#planning #roadmap #mvp #trade-offs #negotiation #scope #stakeholders

Ready to run

npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill scope-negotiate-heaptracetechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-negotiate
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/business/scope-negotiate
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill scope-negotiate-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Takes an oversized feature list, conflicting stakeholder priorities, or a scope disagreement and produces a clear, agreed-upon scope with documented trade-offs. Defines the MVP, phases future work, communicates technical constraints in business terms, and gives stakeholders the information they need to make good decisions.

Core Features & Use Cases

Structured scope negotiation toolkit: inventory all asks, classify must-have vs nice-to-have, define MVP, and plan phased delivery.
Trade-off framing and decision templates to keep stakeholders aligned and signed off.
MVP-first roadmapping with Phase 1 delivery and Phase 2 planning to manage risk and expectations.

Quick Start

Inventory all asks, classify must-haves, define the MVP, and outline Phase 1 deliverables.

Frequently Asked Questions about scope-negotiate

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

FAQPage Schema

How do I negotiate project scope with stakeholders when feature requests exceed available resources?▼

Scope negotiation resolves resource conflicts by inventorying all stakeholder requests, classifying them as must-have or nice-to-have, and defining a clear MVP. This process produces documented trade-offs and formal sign-off to align expectations with constrained delivery capacity.

What is the best way to define an MVP from a large backlog of conflicting stakeholder priorities?▼

Defining an MVP requires applying structured criteria to separate must-have features from nice-to-haves. This classification frames technical constraints in business terms, enabling stakeholders to make informed decisions and agree on a phased delivery plan.

How do I create a trade-off matrix for product roadmap planning?▼

A trade-off matrix for roadmap planning maps feature requests against risk and resource constraints. This structured framing communicates technical limitations in business terms, providing stakeholders the context needed to approve phased delivery and formal sign-off.

Can I use structured scope alignment to manage technical constraints and phased delivery?▼

Structured scope alignment manages technical constraints by defining an MVP-first roadmap with Phase 1 delivery and Phase 2 planning. This approach mitigates risk, sets clear expectations, and documents formal stakeholder sign-off for each phase.

When do I need formal stakeholder sign-off documentation for scope decisions?▼

Formal stakeholder sign-off documentation is needed when projects have large feature lists and constrained resources. It prevents misaligned expectations by recording agreed-upon trade-offs, MVP definitions, and phased delivery plans.

Why does communicating technical constraints in business terms help with scope negotiation?▼

Communicating technical constraints in business terms helps scope negotiation by giving stakeholders the information they need to make good decisions. It translates resource limitations into business impact, facilitating agreement on MVP boundaries and phased delivery.