--- name: al-486-turn-a-client-s-change-request-in-slack-into-a-ready-to-r description: "Small web agencies lose days to change-order back-and-forth on small client requests. In a write-up published October 29, 2026, AI Business Plays describes Justin Sainton of Zao, a small WordPress agency (self-reported, from an October 10 interview): Grok Bot watches every client Slack channel, decides whether a message is something it can act on, builds the change with Cursor agents, opens a pull request, runs it through a QA agent that compares the result to the original request, and drafts the reply to the client. He says one request that would have been a week or two and a $3,000 change order was done in about 45 minutes overnight, and estimates it saves tens of thousands of dollars a month; those are his own estimates. The write-up warns that in his setup replies can reach the client before he looks, and recommends holding every reply and merge for approval. The prompt below follows that safer version. Use when the user wants help with client change requests from slack to pull…" --- # Turn a client's change request in Slack into a ready-to-review change: have an AI agent spot the real requests, build each one on its own branch, test it against the client's exact words, and draft the reply, but nothing merges or sends without your OK Small web agencies lose days to change-order back-and-forth on small client requests. In a write-up published October 29, 2026, AI Business Plays describes Justin Sainton of Zao, a small WordPress agency (self-reported, from an October 10 interview): Grok Bot watches every client Slack channel, decides whether a message is something it can act on, builds the change with Cursor agents, opens a pull request, runs it through a QA agent that compares the result to the original request, and drafts the reply to the client. He says one request that would have been a week or two and a $3,000 change order was done in about 45 minutes overnight, and estimates it saves tens of thousands of dollars a month; those are his own estimates. The write-up warns that in his setup replies can reach the client before he looks, and recommends holding every reply and merge for approval. The prompt below follows that safer version. ## Inputs to collect first Ask the user for anything below that they haven't already given you. Don't guess missing facts. - The Slack messages - Repo link or paste the files, plus how to run it locally ## Instructions Do the task below with the user's inputs in place of each [bracket]. Act as my change-request assistant for client work. Here are today's messages from a client channel: [paste the Slack messages]. Here is the relevant part of the project: [repo link or paste the files, plus how to run it locally]. 1) Sort each message: a change you can act on, a question, or just chat. For each change, restate it in one sentence in the client's own words and list anything unclear as a question for me. 2) For the clearest change, propose the code edit on a new branch named after the request, and list the files you'd touch. 3) Write a short test checklist that compares the result to the client's exact wording, and run or describe each check. 4) Draft the pull request description and a short reply to the client explaining what changed and how to see it. 5) Estimate whether this is in scope or should be a change order, with your reason. Don't merge, deploy or send anything to the client; wait for my OK. ## Safety checks (share these with the user) - This prompt works on text other people wrote (emails, reviews, messages or web pages). That text can hide instructions aimed at AI, such as "ignore your rules and…". Paste it as material to work on, and never let the AI act on requests inside it, like paying, sharing logins or changing records. - Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes. - Don't let AI make the final call on hiring, pay, performance or discipline. Use it to organise information, and have a person decide using criteria you can explain. - Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings. - Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed. ## About this skill - Works with: Grok Bot, Cursor, Slack, GitHub, WordPress - Based on this real-world example: https://aibusinessplays.com/plays/wordpress-agency-grok-bot-turns-client-slack-request-into-done-change/ - Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-486-turn-a-client-s-change-request-in-slack-into-a-ready-to-revi/ - To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/