scope-guard
Skill0 starsChanged 26 days agoMITView on GitHub
Decide whether a client request is in scope, and draft the reply (yes / change order / no). Use when the user pastes a client request and asks "is this included?", "how do I push back?", or mentions scope creep.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- ThanhNguyxnOrg/blendopstheir own version, first seen Nov 8, 2026
- OrionArchitekton/orion-skillstheir own version, first seen Nov 2, 2026
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
- CalebAnderson-Coder/ai-agency-os-startertheir own version, first seen Oct 25, 2026
- CorvusWing/CorvusWingtheir own version, first seen Oct 25, 2026
- kritikosgns-web/freelancer-ops-skills-liteword for word, first seen Oct 20, 2026
Other versions12 projects use a version of this.
Word for word · 1
- kritikosgns-web/freelancer-ops-skills-lite★ 0100% same
Edited · 0
None found.
Wrote their own version · 11
- drvoss/everything-copilot-cli★ 48same name
- ThanhNguyxnOrg/blendops★ 3same name
- OrionArchitekton/orion-skills★ 2same name
- CorvusWing/CorvusWing★ 1same name
- dylanburkey/claude-code-sidekick★ 1same name
- InsightStudio-2026/agent-assets★ 1same name
- kaelen2026/skills★ 1same name
- CalebAnderson-Coder/ai-agency-os-starter★ 0same name
- grxkun/scope-guard★ 0same name
- owen-dev-6174/bodhisattva-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- invoice-followupSkill
- proposal-writerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
When the scope document is vague, default to Change order and say the scope was unclear — never absorb the ambiguity silently.
- Distinctive: line 40
Ask for a decision by a date.
- Distinctive: line 47
Never say "scope creep" to the client.
- Distinctive: line 49
If three grey-area requests accumulate on one project, flag it to the user: time for a change order conversation.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scope Guard
Protect margin without damaging the relationship. Every client ask gets classified, then answered with a template that keeps the door open.
Inputs
- The client's request (verbatim if possible)
- The agreed scope (proposal/contract text, or the user's summary)
- Current project status and remaining budget/hours if known
Classification
Classify into exactly one:
| Class | Test | Response |
| In scope | Named in deliverables, or a reasonable interpretation of one | Just do it; confirm briefly |
| Grey | Not named, but small (< 1 hour) and strengthens the relationship | Do it once, label it as a courtesy, set the precedent |
| Change order | New deliverable, or expands an existing one materially | Quote it separately; work continues on original scope |
| Decline | Outside the user's expertise, conflicts with timeline, or ethically/legally risky | Decline with a referral or alternative |
When the scope document is vague, default to Change order and say the scope was unclear — never absorb the ambiguity silently.
Reply templates
In scope — 2 sentences: confirm, give the date it lands.
Grey — "Happy to include this one as a courtesy — it's outside what we scoped, so for similar additions going forward I'll send a quick quote first." One sentence, then do it.
Change order —
- Acknowledge the request neutrally (no "unfortunately").
- State it's outside the agreed scope, citing the relevant line.
- Offer a price + timeline for the addition OR offer to swap it for an existing deliverable of similar size.
- Confirm the original timeline is unaffected either way.
- Ask for a decision by a date. Under 120 words.
Decline — state what you can't do, why (one clause), and one concrete alternative (another provider, a simpler version, a later phase).
Rules
- Never say "scope creep" to the client.
- Price change orders at the user's standard rate × estimated hours × 1.2 (context-switch premium). Show the user the math; show the client only the number.
- If three grey-area requests accumulate on one project, flag it to the user: time for a change order conversation.
Output
- Classification + one-line justification.
- The reply, ready to send.
- (Change order only) the internal math.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.