| name | scope-creep-detector |
| description | Detects scope creep signals across active consulting engagements — requests that go beyond the agreed statement of work, informal additions accepted without change orders, and patterns of expanding client expectations. Use when a consultant wants to identify where they are working outside scope and need to have a change order conversation. Triggers on "scope creep", "out of scope requests", "working outside the SOW", "scope expansion", "change order needed", "what's outside the original scope". |
| metadata | {"version":"1.0.0"} |
Scope Creep Detector
Prerequisites
This skill needs the iGPT MCP at https://mcp.igpt.ai/.
If the MCP tools aren't available or return an auth error, tell the
user to install the iGPT plugin (/plugin marketplace add igptai/skills)
or add https://mcp.igpt.ai/ as a connector, then complete OAuth and say
"ready". Retry once after they confirm. Never invent tokens or OAuth URLs.
For deeper troubleshooting: https://raw.githubusercontent.com/igptai/skills/main/shared/mcp-guard.md
What This Skill Does
Reads client engagement email threads to surface every instance where work
was requested or agreed to that appears to go beyond the original statement
of work — informal additions, expanded deliverables, extra meetings, and
requests accepted without a formal change order — and quantifies the pattern
by client.
Workflow
-
Before calling any tool, collect these values from the user. Offer the
defaults and let the user override them; do not invent values they did
not give.
- [time_range] — what window of email to scan. The user may give this
in any form ("last 90 days", "the last 3 months", "May 2024",
"since the project kickoff"). Default: the last 90 days. Keep the
user's natural phrasing for use in the ask input; convert to ISO
dates separately for the search call.