Change Announcement With the Pushback FAQ

When to use it

The user has to tell a group of colleagues about a change that affects how they work: a new tool, a new process, a reporting line change, a policy, a move, a shutdown of something people liked. They give the facts of the change and get an announcement plus an FAQ written from the objections, not from the project plan.

Also for checking an announcement the user already drafted: the skill writes the objections, tests the draft against them, and returns the draft fixed.

Not for: announcements to customers, press or the market; redundancy or dismissal notices (those follow a legal process with HR and counsel); or a change the user has not decided yet (that is a consultation, and the skill will say so).

What it asks you

Ask in one message, numbered. Work from what comes back.

1. What is changing, in two or three lines, and what is it replacing?
2. Who is affected, and roughly how many people in each group (for example 40 in sales, 12 in finance)?
3. When does it take effect, and what are the dates between now and then?
4. Why is it being done? Give the real reason, even if it is cost. What was wrong with the current state?
5. What does each affected group lose, and what do they gain? Be honest about the losses.
6. What is already decided, what is still open, and who decides the open points?
7. Who is sending this, who else has signed it off, and where do questions go?
8. Is there anything you know people will say, from corridor talk or earlier meetings?

A vague answer to 4 gets one follow-up: "If an employee asked you in the lift why this is happening, what would you say?" If the honest reason is not one the user will put in writing, the skill says the announcement will read as evasive and asks which part of the truth can be stated.

Never invent a date, a number, a reason, a benefit or a sign-off. Where a fact is missing and the FAQ needs it, the answer reads "not decided yet; decision by name, date" with the name and date from the user, or "not given".

What comes back

Plain text.

OBJECTIONS (the five, ranked, with group, loss and the move used to answer) 1. ...

ANNOUNCEMENT Subject: ... (the announcement) (N words; range 200 to 400)

FAQ 1. Question in the first person Answer. (five in total)

FOR THE MEETING (second tier questions, if any, with one-line answers)

MANAGER COVER NOTE (two lines, sent an hour ahead)

Sequence: who hears it first, how, then who, in three lines. CONFIRM: any date, number or reason the user gave that the skill could not trace to a source, as a question (only if needed). Next: one line naming the single most useful next step.

For a draft the user wrote: OBJECTIONS first, then the fixed announcement, then "What changed:" in at most five lines, biggest gap first.

• 00_START_HERE.pdf: the two-minute set-up for each AI.
• 1 - Skill: change-announcement-with-pushback-faq.zip, one upload to Claude, ChatGPT, Gemini, Grok or Microsoft 365 Copilot. It switches on by itself when this job comes up.
• 2 - Text file for any AI: the same Move as one .txt. Attach it to any chat, on any plan, and type "Follow this file".

It drafts, you read and send. It never contacts anyone for you and never invents a fact, a number or proof.

A Move is a single play. The whole function in a box is an agent pack.