Prepare for a conversation you've been avoiding
Works out what you actually want from it, what the other person is likely protecting, and the first two sentences — the part everyone rehearses badly.
Declines a request clearly, without the apologising, over-explaining, or fake availability that turns a no into a maybe and gets you asked again next week.
Help me say no. THE REQUEST: {{REQUEST}} THE REAL REASON: {{WHY_NOT}} WHO'S ASKING: {{RELATIONSHIP}} First, tell me honestly: **should this be a no?** Given what I've said, is declining the right call, or am I avoiding something I should just do? One short paragraph. If it should be a yes, say so and stop. If it's a no, write the reply: - Decline in the first sentence. Not the third. - One reason, not three. Stacking reasons sounds like an excuse and invites negotiation on each one. - Do not apologise more than once, and not at all if I have done nothing wrong. - Offer an alternative only if I would genuinely do it. Never invent availability I do not have. - End without leaving the door ajar. No "maybe next quarter" unless I mean it. Then flag: **what could make them ask again?** Any phrasing that reads as a soft no rather than a no. Keep it under 80 words and match how I would actually talk to this person.
A prompt is a skill with the serial numbers filed off. Install it once and your agent reaches for it on its own.
Paste this into ChatGPT, Claude Code, Codex, Cursor, or whatever you use:
Install the say-no-and-keep-the-relationship skill globally from https://promptsbuddy.com/prompts/say-no-and-keep-the-relationship/skill.md.claude/skills/say-no-and-keep-the-relationship/SKILL.md
---
name: say-no-and-keep-the-relationship
description: "Declines a request clearly, without the apologising, over-explaining, or fake availability that turns a no into a maybe and gets you asked again next week. Use when the user asks for help with communication tasks like communication, boundaries, email."
license: CC-BY-4.0
metadata:
source: https://promptsbuddy.com/prompts/say-no-and-keep-the-relationship
author: "Rony"
version: "1.0"
---
# Say no and keep the relationship
Declines a request clearly, without the apologising, over-explaining, or fake availability that turns a no into a maybe and gets you asked again next week.
## Inputs to collect first
Ask the user for anything below that they have not already given you. Do not
invent values for these.
- `REQUEST` — What was asked, pasted or described. (e.g. Can you join the Thursday steering committee? It's weekly, 90 minutes.)
- `WHY_NOT` — The real reason, even if you wouldn't say it out loud. (e.g. It's not my area, and I'd be there to make someone else's meeting look important.)
- `RELATIONSHIP` — Who's asking and what you need the relationship to survive as. (e.g. A peer in another team I'll need favours from next quarter.)
## Instructions
Help me say no.
THE REQUEST:
{{REQUEST}}
THE REAL REASON:
{{WHY_NOT}}
WHO'S ASKING: {{RELATIONSHIP}}
First, tell me honestly: **should this be a no?** Given what I've said, is
declining the right call, or am I avoiding something I should just do? One
short paragraph. If it should be a yes, say so and stop.
If it's a no, write the reply:
- Decline in the first sentence. Not the third.
- One reason, not three. Stacking reasons sounds like an excuse and invites
negotiation on each one.
- Do not apologise more than once, and not at all if I have done nothing wrong.
- Offer an alternative only if I would genuinely do it. Never invent
availability I do not have.
- End without leaving the door ajar. No "maybe next quarter" unless I mean it.
Then flag: **what could make them ask again?** Any phrasing that reads as a
soft no rather than a no.
Keep it under 80 words and match how I would actually talk to this person.
## Notes from people who use this
- The honesty check catches the times you're avoiding, not declining. It says yes more often than you'd expect.
- One reason. Three reasons is a negotiation surface.
- The 'could they ask again' flag is what stops the same request returning every month.
---
Say no and keep the relationship · by Rony · v1.0
From PromptsBuddy — https://promptsbuddy.com/prompts/say-no-and-keep-the-relationship
Licensed CC BY 4.0.
Every prompt is also available at /prompts/say-no-and-keep-the-relationship/skill.md — see all install options.
The instinct under pressure is to justify — to stack three reasons so the no feels defensible. It has the opposite effect. Each reason is something the other person can solve ("we can move it to Tuesday"), and by the third you have built them a map of how to get a yes.
Most nos that get re-asked were never heard as nos. "Probably not right now", "let me see how the quarter goes", "maybe once this ships" all read as maybe. The final check exists because you cannot usually spot this in your own writing.
Works out what you actually want from it, what the other person is likely protecting, and the first two sentences — the part everyone rehearses badly.
Front-loads the one thing that changed, states what's at risk without hedging, and makes the ask explicit — so the person who reads only the first line still gets it.