scope-creep-response
Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how do I say that's out of scope nicely, or write a change order email. Produces the classification of the ask, the graduated response with ready-to-send wording, and the contract language that prevents the rerun.
npx skills add mohitagw15856/pm-claude-skills --skill scope-creep-response --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Scope Creep Response Skill Scope creep is rarely malicious — it's a client who genuinely can't tell the difference between "small tweak" and "new workstream," talking to a freelancer afraid that any boundary costs the relationship. The damage comes from the two failure modes: absorbing everything silently (resentment, then a blowup over something trivial) or lawyering every request (death by friction). This skill runs the middle path: classify honestly, respond proportionally, and make the *structure* hold the boundary so the person doesn't have to. ## What This Skill Produces - **The classification** — in-scope / gray / clearly-out, argued against the actual agreement text, including the honest case for the client's reading - **The graduated response** — goodwill grant, flag-and-track, change order, or renegotiation — with ready-to-send wording - **The change-order artifact** — small, friendly, priced; a form not a confrontation - **The prevention layer** — scope language, revision counts, and the "great idea — phase 2" ritual for the next contract ## Required Inputs Ask for these if not provided: - **What the agreement actually says** — the scope text verbatim; if scope was nev
- What This Skill Produces
- Required Inputs
- Framework: The Graduated Response Rules
- Output Format
- Classification
- The Move
- Change Order (if applicable)
- Prevention (next contract / next phase)
- Quality Checks
- Anti-Patterns
What does the scope-creep-response skill do?
Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how do I say that's out of scope nicely, or write a change order email. Produces the classification of the ask, the graduated response with ready-to-send wording, and the contract language that prevents the rerun.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill scope-creep-response --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.