跳到正文
cccskills
免费在 GitHub 公开

next-step-and-handoff

Use when a sales call wrapped up with no firm next step, a live deal has stopped answering, or a won deal has to pass cleanly to closing or implementation.

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

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

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

Next step and handoff

Use this when a call ended with nothing anyone could put in a calendar, a moving deal went silent, or a signed deal must land with the team that closes or implements it. Work from how the last call ended, what both sides agreed, the deal sheet, and who receives any handoff.

Grade the next step

A real next step passes four tests: it has a date, it has a time, it sits on both calendars, and the buyer has homework due before it. Name every test it fails. Then find the point in the transcript where the rep should have locked it in, quote it, and write the one or two sentences that would have closed it there, finishing on a specific ask.

Draft the follow-up

Lead with a subject line. The body is four to six sentences, in this order: the problem as the buyer described it, in their own words; the agreement you reached; your deliverables and when they land; the buyer's deliverables; and a single ask pinned to a day and an hour. Keep your pitch out, and include nothing the buyer did not actually agree to; an invented deadline costs more trust than a thin email.

For a deal already gone quiet, write a short re-open instead: the last thing they said mattered, one fresh reason tied to their business to talk now, and one proposed date.

Build the handoff packet

Buyer outcome, key contacts with roles, what was promised (quoted, never paraphrased into more), open loops with owners and dates, and the top risk. Reconcile every open commitment across the deal sheet, mail, and notes so no promise leaks. Show the draft or packet in chat, then save it dated.

What you hand back

The four-test verdict with the better line, plus whichever the moment needs: the follow-up, the re-open, or the handoff packet.

Fallbacks

No agreement at all means you open by saying so, then write the re-open instead of recapping a thread that never existed. A handoff with open loops nobody owns means you name the gaps and ask who takes each before the packet ships.

Approval gate

Drafts only, nothing sends and no handoff ships without your explicit yes.

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题