Change Control / Scope Management

Purpose

• Evaluate, manage, and formalize changes to project scope to ensure transparency, impact awareness, and controlled decision-making. This skill protects the original agreement and avoids implicit acceptance of scope changes.

Design principle

• This skill DOES NOT detect changes automatically. It accepts change_request inputs (informal or structured) and answers: Is this a change? If so, is it in-scope, out-of-scope, or unclear? What is the impact? What options exist?

What counts as a change

• Valid inputs include: client requests, new functional/technical requirements, priority shifts, changes to assumptions or constraints (deadlines, resourcing, compliance), or repeated small adjustments indicating scope creep.