Ask the model to find the scope creep in a project brief before anyone signs it

Scope creep rarely arrives as one obvious extra ask. It arrives as a dozen small, individually reasonable additions to a brief - "and while we're at it", "it'd also be useful if" - each of which reads fine in isolation and adds up to a project that's quietly twice the size of the one that got approved.

Before a brief goes for sign-off, paste in the original goal alongside the current draft and ask specifically: which parts of this serve the original goal, and which parts have been added since that don't? Not "review this brief" - that gets you a grammar check. The specific comparison against the stated goal is what surfaces the line that's technically useful but never actually agreed.

It won't catch everything, and it isn't a substitute for someone senior actually reading the thing - but it's a fast first pass that turns "does this feel bigger than it used to be" into a concrete list of exactly which lines to ask about, before the brief is the thing everyone's already agreed to and scope creep becomes a fight about broken promises instead of a five-minute conversation about a checklist.