Individual skill
scope-creep-defense
Detects scope creep and converts it to paid work using the new-request test, a one-yes courtesy budget, a word-for-word change-order script, and a relationship-preserving no. Use when a freelancer says "the client keeps asking for little extras", "this project has doubled and the price hasn't", "how do I say no without losing the client", "they want one more quick thing", "can I charge for this add-on", or "the retainer hours are gone but requests keep coming". Do NOT use for writing the contract clauses that make this enforceable - use statement-of-work-writer instead; this skill enforces at delivery time what that skill establishes at signing.
skills/scope-creep-defense/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,612 bytes
Read excerpt
# Scope Creep Defense
Scope creep never arrives as a demand; it arrives as a compliment - "you're so good at this, could you also just..." - and each individual yes is small enough that refusing feels petty. The costly mistake this skill prevents is the accumulation: ten small yeses that turn a fixed-price engagement into an unpaid custom one, followed by resentment the client never saw coming because nobody told them the meter existed. The defense is not saying no more often; it is converting requests into revenue through a process the client experiences as professionalism.
This skill pairs with statement-of-work-writer - it enforces the inclusions, exclusions, and change-order clause written there, and it is nearly toothless without them. Worked example: Maya, a freelance brand designer on a $4,900/month Brand System Retainer (up to 36 hours, 2 revision rounds per deliverable) with a DTC hot-sauce brand.
## Operating procedure
### Step 1: Collect the inputs
1. The signed SOW: inclusions, exclusions, revision limit, change-order clause. If no SOW exists, the honest answer is that scope cannot creep past a boundary that was never drawn - do statement-of-work-writer first and apply this skill from the next request onward.
2. The specific request, verbatim if possible.
3. Courtesy budget status: has the one free yes for this project already been spent?
4. Hours consumed against the retainer or budget this cycle. Label estimates as guesses.