mh-coo-scope-management

Classify scope changes, assess impact, and draft change orders.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-scope-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mh-coo-scope-management
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/coo/delivery-ops/mh-coo-scope-management
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-scope-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mh-coo-project-delivery-framework, mh-coo-quality-assurance, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps manage scope changes during active engagements, ensuring that all additional work is documented, priced, and signed off before it begins, protecting both MicroHard's economics and the client relationship.

Core Features & Use Cases

  • Scope Change Identification: Distinguishes scope changes from clarifications or rework requests.
  • Change Classification: Classifies changes as additive, substitutive, or subtractive.
  • Impact Assessment: Assesses the impact on delivery timeline and price.
  • Change Order Drafting: Produces formal change orders in client-ready language.
  • Sign-Off Process: Manages the two-stage sign-off process with Imad and the client.
  • Documentation: Writes detailed scope management records for internal governance.
  • Use Case: When a client requests additional work or a change that falls outside the agreed scope of an engagement, this Skill documents it, prices it, and gets it signed off before any additional work begins.

Quick Start

Run the scope management workflow to handle a scope change request.

Frequently Asked Questions about mh-coo-scope-management

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

FAQPage Schema
How do I manage project scope changes and document client requests during an active engagement?

Manage project scope changes by distinguishing requests from clarifications, classifying them, assessing timeline and price impacts, drafting change orders, and facilitating sign-off to protect delivery economics.

What is the difference between a scope change and a clarification in engagement management?

A scope change in engagement management introduces additive, substitutive, or subtractive work outside agreed boundaries, while a clarification refines existing scope without altering pricing, timeline, or requiring a formal change order.

How do I draft a change order for additional work requested by a client?

Draft a change order by classifying the additional work request, assessing its impact on delivery timeline and price, and producing formal documentation in client-ready language for the two-stage sign-off process.

Does this scope management workflow support the sign-off process for delivery operations?

Yes, the scope management workflow supports delivery operations by facilitating a two-stage sign-off process, ensuring internal governance and the client formally approve change orders before additional work begins.

What is the best way to assess the impact of a subtractive scope change on project economics?

Assess subtractive scope change impact on project economics by classifying the change, evaluating its effect on the delivery timeline and price, and documenting the adjustments in detailed internal governance records.

When do I need to run a scope management workflow for engagement management?

Run the scope management workflow for engagement management whenever a client requests work or modifications falling outside agreed boundaries, ensuring all changes are priced, documented, and signed off.