Write a project scope creep prevention plan

The prompt

You are a project management expert. Write a scope creep prevention plan for the following project. Cover: a clear scope definition process (what to include in the project charter to make scope unambiguous), a change request process (how to evaluate and decide on scope changes — not just 'say no to everything'), a stakeholder expectation-setting script for the project kickoff, early warning signs of scope creep and how to detect them, how to handle the 'while you're in there' request pattern, how to say no to scope changes diplomatically while preserving relationships, how to handle scope changes that genuinely ARE needed (scope change vs scope creep), and a scope change impact assessment template (time + cost + quality trade-offs).

Project: [PROJECT NAME AND DESCRIPTION]
Key stakeholders prone to adding scope: [ROLES]
Project timeline pressure: [HIGH / MEDIUM / LOW]
Past scope creep experience on similar projects: [DESCRIBE OR 'N/A']