跳到正文
cccskills
免费在 GitHub 公开

hard-news

Prepare to deliver difficult technical news to a client — a conversational prep session before the hard conversation happens

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Behavior

This is a prep session. The goal is to walk into a hard conversation clear-headed, not rehearsed. Start by understanding the situation conversationally — one question at a time.

Open with:

"Tell me what happened — the version you'd say to a colleague, not the client. Don't soften it yet."

Wait for their answer. Then ask what matters most for shaping the conversation:

"What do you know about how this client handles bad news? And what do you need from this conversation — what's the outcome you're steering toward?"

Wait for their answer. Then, before preparing anything:

"Write your opening two sentences right now — the actual words you'd say to start this conversation. Don't polish them, don't second-guess them. Just write what comes out."

Wait for their draft. This is the most important step — it reveals how they instinctively handle pressure. Open the prep with honest feedback on their draft: what's working, what would land badly, and what to change.

Then deliver the full prep. Keep it tight — they need to be able to hold this in their head going into the conversation:

The news in one sentence — the clearest, most honest version. No jargon, no hedging, no burying the lead.

How to open — the first 3–4 sentences verbatim. Lead with the news, not a preamble. Bad news after small talk feels like manipulation. Name the problem directly, take appropriate accountability without over-apologising, signal there's a plan.

The explanation — how to describe what happened in plain terms the client understands. What happened, why, what you know vs. what you're still figuring out, and what it means for the project.

The path forward — what you're proposing. Specific, not vague. If the plan isn't complete yet, say what you do know and when you'll have more.

Likely reactions — 2–3 reactions given what you know about this client, and how to respond to each. Non-defensive, grounded. Defensiveness signals you care more about being right than solving the problem.

What not to say — 2–3 specific phrases or moves to avoid. Things that feel natural under pressure but damage trust: over-apologising, deflecting blame, minimising impact, over-promising.

Close with:

"What did your unpolished opening reveal about how you instinctively handle discomfort? Did you soften, deflect, or lead straight?"

Wait for their answer. Respond with one short paragraph: what their draft pattern reveals about their default communication instinct under pressure, and the one habit worth practising.

Tone

Direct and empathetic. This is not a script to hide behind — it's a thinking tool to enter the conversation clear-headed. The user should feel prepared, not rehearsed.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

challenge

免费

Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

explain

免费

Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have."

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

offboard

免费

Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

prior-art

免费

Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.

中文简介正在准备中。当前显示原文说明。

thoughtbot/rails-consultant262026年9月19日 更新

查看 thoughtbot 的全部技能

报告此技能的问题