More screenshots
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsautomation client change request manager
Converts vague client requests into structured change briefs while identifying scope creep, maintenance boundaries, technical impact, and approval requirements.
$9.99
automation client change request manager
Example session with this skill installed
A client sent this
"Hey, can we quickly add WhatsApp notifications to the lead automation? Also, can you make the AI better at spotting really hot leads and send those directly to the senior sales rep? I think both should be small changes.
The current workflow takes website form submissions, uses AI to qualify the lead, creates a HubSpot record, and sends a sales email.
We have a standard maintenance agreement, but I don't have the full contract with me right now.
Please tell me what is actually maintenance, what is a change request, what hidden work is involved, and what I should clarify with the client before agreeing."
- Read your context and instructions
- Compiled the automation client change
Change Request Assessment
Executive Summary
The client's message contains two distinct requests that should be assessed separately.
- Add WhatsApp notifications to the existing lead automation.
- Change the AI qualification logic so that "hot" leads are identified and routed to a senior sales representative.
Neither request should automatically be treated as routine maintenance based on the information provided.
The maintenance agreement has not been supplied, so contractual treatment cannot be verified.
Request 1 — WhatsApp Notifications
| Attribute | Assessment |
|---|---|
| Request | Add WhatsApp notifications to the existing lead automation |
| Technical Classification | NEW CAPABILITY |
| Secondary Classification | INTEGRATION ADDITION |
| Contractual Treatment | UNKNOWN — contract not provided |
| Scope-Creep Risk | HIGH |
| Technical Impact | MODERATE to HIGH |
| Approval Status | NOT VERIFIED |
Hidden technical work
Potential additional work includes
- WhatsApp provider selection or configuration
- Authentication and credentials
- Message templates and recipient rules
- Phone-number validation
- Consent and communication requirements
- Message failure handling
- Retry behavior
- Duplicate-message prevention
- Rate limits and provider restrictions
- Testing across successful and failed delivery scenarios
- Deployment and configuration changes
- Documentation and maintenance implications
This should not be treated as a simple notification wording change without further evidence.
Request 2 — HOT Lead Classification and Senior Routing
| Attribute | Assessment |
|---|---|
| Request | Identify HOT leads and route them to a senior sales representative |
| Technical Classification | EXISTING BEHAVIOR ADJUSTMENT / NEW BUSINESS LOGIC |
| AI Classification | MATERIAL AI BEHAVIOR CHANGE |
| Contractual Treatment | UNKNOWN — contract not provided |
| Scope-Creep Risk | HIGH |
| Technical Impact | HIGH |
| Approval Status | NOT VERIFIED |
Why this is a material change
The requested change modifies how the AI makes a business decision.
The workflow currently qualifies leads.
The new request introduces
- A new HOT classification.
- Criteria for determining whether a lead is HOT.
- Potential changes to the AI prompt or decision logic.
- A new routing condition.
- Assignment of HOT leads to a senior representative.
- Additional downstream CRM behavior.
- Potential notification changes.
- New fallback behavior when the AI is uncertain.
The business definition of "HOT" is currently undefined.
Acceptance Criteria That Need Clarification
Before implementation, clarify:
- What exactly qualifies a lead as HOT?
- Which fields or signals should the AI use?
- What confidence threshold is required?
- What happens when the AI cannot determine the classification?
- Which senior representative receives the lead?
- What happens when that representative is unavailable?
- Should HOT leads receive a different notification?
- Should existing qualified/not-qualified behavior remain unchanged?
- How should incorrect HOT classifications be handled?
- What testing evidence is required before deployment?
Contractual Assessment
The maintenance agreement has not been supplied.
Therefore
CONTRACTUAL TREATMENT: UNKNOWN / REQUIRES CONTRACTUAL CLARIFICATION
Do not assume either request is included in maintenance.
The technical classification should be completed first. Contractual treatment should then be determined from the actual agreement.
Scope Boundary
Existing Scope
Website form → AI lead qualification → HubSpot → sales email
Requested Change
Add WhatsApp notifications.
Add HOT-lead classification.
Add senior-sales routing.
Potential Additional Work
- New messaging integration
- Authentication
- New business rules
- AI prompt/logic changes
- CRM routing
- Error handling
- Retry and duplicate prevention
- Testing
- Deployment
- Documentation
- Ongoing maintenance considerations
Recommended Next Action
Do not approve implementation yet.
Ask the client to clarify the definition of HOT leads and provide the applicable maintenance agreement or relevant contract terms.
Then create separate change assessments for the WhatsApp integration and HOT-lead routing.
FINAL STATUS: INFORMATION REQUIRED
APPROVAL STATUS: NOT VERIFIED
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Vague client feedback like "just a quick tweak" can lead to undocumented scope creep, unexpected development work, and disagreements over what maintenance actually covers. Automation freelancers and agencies need a consistent way to determine whether a request is maintenance, optimization, a billable change, or a completely new project.
What it does
- Converts informal client messages into structured change request briefs.
- Classifies the technical nature of each requested change.
- Separates maintenance, optimization, new capabilities, expansions, and new workflows.
- Analyzes hidden technical work across integrations, data, AI behavior, permissions, testing, deployment, and documentation.
- Detects potential scope creep without automatically assuming that every change is billable.
- Compares requests against supplied maintenance agreements or contracts.
- Defines observable acceptance criteria for requested changes.
- Identifies missing information, dependencies, risks, and blocking unknowns.
- Handles multiple client requests and prioritizes them using deterministic operational criteria.
- Produces a client-ready change assessment and recommended next action.
Built for AI automation professionals
Designed for freelancers, consultants, and agencies managing automations built with n8n, Make, Zapier, AI agents, APIs, CRMs, forms, databases, email systems, and other connected business workflows.
What you can give it
- A client message or change request
- The existing workflow description or configuration
- A maintenance agreement or contract
- Evidence of an existing incident
- Multiple requests from different clients or workflows
What you get
The skill produces a structured assessment covering technical classification, contractual treatment, scope-creep risk, technical impact, acceptance criteria, approval status, blocking unknowns, recommended next action, and final status.
Important limitation
The skill does not claim to inspect, modify, test, deploy, approve, or monitor a live automation unless the necessary evidence or tools are actually provided. It clearly separates verified facts from observations, inferences, potential risks, and unknowns.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 8 days ago
- Passed all security checks, Safe to install