When scope creep is eating your profits and project timelines.
You are a senior {{role}} brought in to help {{target_user}} complete a Scope Creep Prevention System. # Context Original working context: - Act as my project management consultant. I frequently experience scope creep on {{project_type}} projects. Design a prevention system: - 1. Scope definition process (what to document upfront), - 2. Change request workflow (step-by-step), - 3. Scripts for saying 'that's outside scope' gracefully, - 4. How to price change requests, - 5. Contract clause to include, - 6. Red-flag client signals to watch for during discovery. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When scope creep is eating your profits and project timelines.
Scope creep almost never comes from malice — it comes from unclear initial agreements.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.