Client Change Delta — Clarify Requests Before You Promise

    1

    Compare client requests with accepted scope. Map conflicts and draft a reply without inventing prices, deadlines or approval.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Client Change Delta — Clarify Requests Before You Promise

    Example session with this skill installed

    Compare the accepted scope and new messages in examples/worked-case.md. Preserve every request and both conflicting CTA instructions. Identify what is known, what is unestimated and which decisions are missing. Draft a reply without confirming Friday or an extra fee.

    • Read your context and instructions
    • Compiled the client change delta

    Synthetic Worked Example — Not a Client Result

    Supplied material

    B1 — accepted proposal: One landing page, one contact form, two design revision rounds. English copy only. Additional integrations require a separate estimate. Acceptance email A1 explicitly accepts B1. No hourly rate, remaining-round count, delivery date or change-approval authority is supplied.

    M1 — client: “Change the button to Book a Demo. Add a Spanish version and connect the form to Salesforce. Friday would be great.”

    M2 — a second stakeholder: “Keep Start Free Trial on the button.” No controlling approval is supplied.

    Worked assessment

    RequestDeltaEvidenceCategoryNext decision
    R1CTA becomes Book a DemoM1; conflicts with M2CONFLICTIdentify the approved CTA and its decision owner
    R2Spanish versionM1; B1 says English onlyCHANGE_CANDIDATEClarify translation ownership and desired scope, then estimate
    R3Salesforce integrationM1; B1 requires separate integration estimateCHANGE_CANDIDATEClarify fields, account access and acceptance, then estimate
    R4Friday deliveryM1; no accepted dateUNVERIFIEDEstablish feasibility and agreement; Friday is requested only
    R5Preserve Start Free TrialM2; conflicts with R1CONFLICTResolve with R1; do not silently select the latest message

    Coverage: 5/5 extracted requests. Effort and price: NOT_ESTIMATED. The evidence does not establish whether R1/R5 uses a remaining revision round. Implementation approval: not supplied.

    Reply draft

    “Thanks — I've captured the Spanish version and Salesforce connection for clarification and estimation. The accepted page scope is English-only, with integrations estimated separately. We also have two different CTA requests; please confirm the approved wording and who signs that off. Friday is a requested date at this point. Once those choices and the integration details are clear, I can assess the scope and timing before we agree a change.”

    This is an author-reviewed example. It is not an independent agent evaluation, a sent message or proof of a client's agreement.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    “Add a Spanish version, connect Salesforce, change the button, and Friday would be great.” Which parts were already agreed? Who approved the CTA? Is Friday a request or a commitment?

    Give Client Change Delta the accepted proposal and the new messages. Receive a source-linked request table, unresolved decisions and a calm reply draft. It separates a covered item, a clarification, a change candidate, a conflict and missing evidence.

    Included

    • Focused English skill instructions and a compact decision-brief template.
    • A synthetic worked case covering five requests, contradictory CTAs and missing estimates.
    • Coverage checks so conflicting or compound requests do not disappear.
    • Clear separation of requested dates, estimates, approval and agreed commitments.

    No original scope? The result says SCOPE_UNVERIFIED. A new request does not automatically become a payable change, and a supplied hourly rate does not authorize extra hours. The reply asks for the decisions needed next without accepting scope, cost or timing for you.

    This is a small text workflow for freelancers and small agencies. It does not run an agency, verify a signed agreement, interpret legal enforceability, calculate a price without inputs or contact your client. The package has no scripts, network calls or accounts to connect.

    Scope and limitations

    The worked case is author-reviewed synthetic material, not a sent message, a real client success story or an independent model evaluation. Output quality varies with source completeness and model judgment. Cross-agent behavior and Agensi delivery remain unverified. No financial outcome or legal protection is promised.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    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

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Requires

    Text-capable SKILL.md host
    Python

    Listedtoday

    What's inside

    Frequently Asked Questions