使其落地
emichy2026-10-28查看 1351复制 315
塑造一条内部信息,使一个合理的押注在转述中存活下来——向团队解释路线图、创始人或高管更新、资源请求——锚定在观察到的客户行为上。当思考是正确的但讲述在稀释它时使用。"帮助我的 CEO 理解这个押注。" / "向团队解释季度路线图。" / "我如何为路线图构建这个?" / "让这个落地。" 仅限内部沟通——不是销售、营销或面向客户的文案。不要用于客户互动……
📘如何使用这个技能
- 1复制技能内容·点击上方「Copy SKILL.md」复制全部内容,或 Download 下载到本地
- 2打开你的 AI 客户端·支持 Claude Code、Trae、Cursor、ChatGPT、DeepSeek、Kimi 等任意 AI 助手
- 3粘贴为系统提示/知识文件·Claude Code:放入 .claude/skills/ 目录;普通对话:作为首条消息发送并说「请严格按这份技能文档执行」
- 4直接提出你的需求·AI 会按技能定义的工作流、格式和约束来处理,无需再解释背景
💡 提示:技能生效后,每次对话只需一句需求,AI 会按 SKILL.md 的流程执行。
SKILL.md2672 chars
--- name: make-it-land description: >- Shapes an internal message so a sound bet survives the retelling — explaining the roadmap to the team, a founder or exec update, a resource ask — anchored on observed customer behavior. Use when the thinking is right but the telling is diluting it. "Help my CEO understand this bet." / "Explain the quarterly roadmap to the team." / "How do I frame this for the roadmap?" / "Make this land." Internal communication only — not sales, marketing, or customer-facing copy. Do not use for customer interviews (prep-customer-interview, review-interview, extract-customer-insights). --- # Make it land Turn rambling into a message that moves a decision. Direct, no hedge — same voice as `pressure-test-a-bet`. ## House style Answer first, in one sentence. Then only the evidence that carries it. Evidence is selected, not gathered — the two quotes that carry it, not the six that mention it. Every section earns its place by changing what they'd do this week; if it doesn't, cut it. Slack, not email. No preamble, no applause, and none of "the move" / "the play" / "the tell" / "the key insight here" / "Here's my take." Applies to how you talk to them *and* to the message you draft. ## Output contract | | Rule | |---|------| | **Line 1** | Insight or ask — not warmup | | **Deliver** | Slack-length + paragraph version | | **Bounce** | If observed behavior exists, lead with it. If it doesn't, name what the message rests on — customer signal, inference, or conviction. Don't invent proof. | ## Structure **Audience → Behavior → Insight → Ask** 1. **Audience** — what do they care about right now? 2. **Behavior** — one observed fact. Not a feature. Not a theme. 3. **Insight** — so what? 4. **Ask** — decide / approve / unblock / align. One per message. One proof point if available: ticket count, anonymized quote, or metric. ## Examples **Before:** "We've been doing discovery on reporting and customers have mentioned wanting better visibility and we think this could be a big opportunity next quarter…" **After:** "Ops managers export to Excel every Monday for a status report their VP never asked for. Ask: one sprint on visibility-without-export, or does [other bet] win? Need a call by Friday." **Before:** "Q3 roadmap: Salesforce integration, reporting improvements, and some performance work. Let me know if you have questions." **After:** "Q3 is one bet: deal context stops dying between our tool and the CRM — reps copy-paste notes today, and 3 of 5 recent churns dropped off when deals got complex. Reporting and perf slip to Q4. Say something now if that breaks a commitment you've made."