Scope Creep Firewall — Classify Change Requests & Draft the Reply

Name: Scope Creep Firewall — Classify Change Requests & Draft the Reply
Price: 12 USD
Availability: InStock
Author: Agensi

by Vivek K

When a client asks for “one more thing,” this skill checks it against your signed scope, tells you in / gray / out, recommends what to do, and drafts a professional reply (it does not send anything).

$12

30-day refund guarantee

Secure checkout via Stripe

0 installsSecurity scanned

See it in action

You say

Project: Harborline Logistics — Ops Dashboard MVP (week 3 of 6) SOW: 4 web views, 2 roles, Postgres read replica, Azure deploy, 2 revision rounds Exclusions: mobile/push, supplier portals, Excel migration, training videos, … Fee: $22,400 fixed · 6 weeks · cutover date fixed

Slack from Priya: "Supplier ASN self-service upload? iOS push for exceptions? Migrate 3 years Excel inventory? Training video? Dark mode if easy?"

Your agent does

Classification: OUT-OF-SCOPE Action: CHANGE-ORDER Confidence: High · Precedent: High

Matches:

Supplier upload → OUT (exclusion: supplier portals)
iOS push → OUT (exclusion: mobile/push)
Excel migration → OUT (exclusion: Excel migration)
Training video → OUT (exclusion: training videos)
Dark mode → GRAY (not in deliverables)

Impact (estimate only): ~55–85 hrs · +2–4 wks if pre-launch · ~$7.7k–$11.9k band Recommend: CO #1 + Phase 2 post-cutover; do not absorb mid-build 3 reply drafts + change-order scaffold + Firewall Log JSON

What you get

Client Slack/email asks for extras mid-projectDecide absorb vs change order vs decline with evidenceDraft a firm but polite reply without burning the relationshipScaffold a paid change order before any out-of-scope work startsLog scope decisions (JSON) for project history or disputes

About this skill

The problem

“Quick addition” requests eat margin and slip launches when teams say yes without checking the signed scope.
Responding from memory leads to inconsistent boundaries, weak change orders, or relationship-damaging pushback.
You need a clear in / gray / out call, impact (including precedent risk), and a reply you can send — not a full new proposal.

What it does

Compares the client’s new ask to your original deliverables, exclusions, and assumptions — with evidence quotes.
Classifies each item as IN-SCOPE, GRAY-ZONE, or OUT-OF-SCOPE.
Estimates effort, timeline, cost band, delivery risk, and precedent risk (will saying yes open the floodgates?).
Recommends an action: ABSORB, CLARIFY, NEGOTIATE, CHANGE-ORDER, or DECLINE.
Drafts three reply tones (collaborative, firm, formal) plus a change-order scaffold when needed, and a Firewall Log JSON.

Not a proposal builder

This skill (firewall): post-sale. You already have a SOW; a change request just arrived.
Proposal / scope builders: pre-sale. They turn discovery notes into tiered packages, pricing, and a full SOW.
Use the firewall to defend scope; use a proposal skill to define and sell scope. Different jobs, different outputs.

Frameworks & tools

Works from any written SOW, proposal excerpt, or statement of work plus the incoming client message.
Stack-agnostic (web, product, marketing, ops tools) — classification is against the agreement, not a framework.
SKILL.md workflow for Claude Code, Cursor, Codex CLI, OpenClaw, and similar agents. No integrations required.

Why this beats prompting it yourself

Evidence table tied to real exclusions/deliverables — not gut feel.
Decision matrix includes precedent risk, not only hours.
Multi-item requests are split and classified line by line.
Three ready reply drafts + CO scaffold so you respond the same day.
Draft only: nothing is sent; estimates stay labeled as estimates; not legal advice.