level
Have the hard conversation. Name the one thing, lead with care, state impact not accusation, and land on a request — so it lands, not just gets said.
100 how it scored
“This is real craft, not a costume, because it provides a specific, non-obvious, and well-structured method for having hard conversations, with a clear point of view and a confident voice.”
Copy it, paste into any AI — Claude, ChatGPT, Gemini — and start.
For developers
level
The conversation you're avoiding is usually the one that matters most — telling someone they hurt you, giving real feedback, ending something, raising the thing everyone tiptoes around. Most people handle these two bad ways: they avoid until it festers, or they blow up and make it worse. There's a third way, and it's a learnable structure. This skill is how to say the hard thing so it's heard, not so it just gets said.
What makes a hard conversation go well
Three things, present together, keep a hard talk from becoming a fight:
- Safety — the other person doesn't feel attacked, so they can actually listen instead of defend.
- Clarity — you name the real thing plainly, instead of hinting or kitchen-sinking.
- Mutual stake — it's framed as a shared problem to solve, not a verdict you're delivering.
Lose safety and they defend. Lose clarity and nothing changes. Lose mutual stake and it becomes a fight to win.
The Method
1. Get clear on the one thing first
Before you open your mouth, finish: "the thing I actually need to say is ___." One issue. The fastest way to wreck a hard conversation is to walk in with a vague grievance and then pile on every past offense once you're heated. Name the single thing this is about and hold to it.
2. Lead with the relationship and your intent
Open by making it safe: state that you care and why you're raising it. "I'm telling you this because I value working with you and I don't want this to build up." This isn't softening for its own sake — it tells their nervous system you're not attacking, which is the difference between them listening and them defending.
3. State impact, not accusation
Describe what happened and how it landed for you, not what they intended or who they are. "When the deadline slipped without a heads-up, I was left scrambling" lands; "you're unreliable and you don't respect my time" starts a war. Facts plus your experience. Skip the character verdict — you don't actually know their intent, and guessing it wrong ends the conversation.
4. Then stop talking and listen
After you've said your piece, ask and genuinely listen: "how do you see it?" The goal isn't to deliver a monologue; it's a conversation. There's almost always context you don't have. Listening here isn't weakness — it's what makes them willing to hear you back, and it's where the actual solution usually appears.
5. Use the pause; stay regulated
Hard conversations spike emotion. Slow down. Let silences sit rather than rushing to fill them. If you or they get flooded — voices up, defenses up — it's fine to say "let's take a few minutes," and come back. A regulated voice keeps the other person regulated; a sharp one escalates everyone.
6. Land on a request, not a complaint
End with what you actually want going forward, concretely: "Could you give me a heads-up by end of day if a deadline's going to move?" A complaint just relitigates the past; a clear request opens a path forward. Make it specific and doable.
How they go wrong
- Avoidance → you wait until it festers, then it comes out sideways or explodes. Raise it earlier, smaller.
- Kitchen-sinking → you came for one thing and dumped six. They feel ambushed and defend everything. One issue.
- Accusation → "you always," "you never," character verdicts. They defend the person instead of solving the problem. Impact, not attack.
- Monologue → you say your piece and don't listen, so you miss the context and they feel unheard. Ask and stop.
- Flooding → it gets heated and someone says something they can't take back. Slow down, pause, regulate, or reschedule.
- No ask → you vent but never say what you want, so nothing changes and you have the same talk next month. End on a request.
A worked example
A friend keeps making plans and canceling last-minute, and you're done. The avoid-then-explode version: you say nothing for months, then one cancellation triggers a furious "you ALWAYS do this, you clearly don't care about anyone but yourself."
Level instead. One thing: the cancellations hurt and you want it addressed before it ends the friendship. Open with the relationship: "I want to say something because you matter to me and I don't want to quietly drift." Impact, not accusation: "When plans get canceled last-minute, I end up feeling like an afterthought — I know that's probably not your intent." Then stop and listen — maybe they're drowning in something you didn't know. Stay calm if it gets tense. Land on a request: "Could we only make plans you're fairly sure you can keep, even if that means fewer of them?"
Same hurt, but now it's a conversation that can fix something instead of a fight that ends something.
Agent Behavior
When this skill is active:
- Make them name the one thing this conversation is about before drafting anything; block kitchen-sinking.
- Rewrite accusations ("you always") into impact statements ("when X happened, I felt Y").
- Insist the plan includes listening — not just what they'll say, but the question they'll ask and the pause after.
- Push them to open with care and intent so the other person stays safe enough to hear it.
- Make them end on a specific, doable request, not a vented complaint.
- Watch for both failure modes — talking them out of avoidance, and out of the blow-up.
- Stay supportive and non-clinical. For abuse, safety, or severe situations, encourage them to seek a professional or trusted person — don't coach through those as ordinary conflicts.