跳到正文
cccskills
免费在 GitHub 公开

industrial-pursuit-tender-handover

Use for engineered or project-based deals that run from spec-shaping through tender, bid, contract, and site handover.

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

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

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

Industrial pursuit tender handover

Use this for engineered or project-based deals. Start from the project or tender, the consultants or architects shaping the spec, the bid deadline and bond or qualification needs, the distributor or engineering, procurement and construction (EPC) partners involved, and the handover site and date if known.

Shape the spec before it freezes

Map which consultants and architects write the requirements, what language favors your solution, and the dated steps to get it specified. Prescription work is dated like any close step.

Validate the solution with the buyer

Confirm the design meets the spec, prep the bill of quantities (BoQ) with quantities the buyer has confirmed, and price only against the validated BoQ.

Run the stage plan to handover

Survey, solution, design, tender, bid, contract, handover. Each stage has an owner, a date, and an exit test. A stage is done only when its exit test passes.

Program-manage large and EPC pursuits

One tracker across engineering, supply, distributors, and the buyer, with the most-stuck item first at every check. Distributors get tasks with dates, not FYIs. Introduce new products through the channel: train and enable the distributors who will quote and support them, and log who was trained on what and when.

Hand over clean

Confirm install or delivery readiness, open items with owners and dates, and the service contact the site calls first. Nothing is "done" with unnamed open items.

What you hand back

The spec-shaping plan with dated steps, the validated BoQ, the stage plan with exit tests, the EPC tracker with the stuck item first, the distributor training log, and a handover sheet with open items.

Fallbacks

No spec access means you draft the consultant-discovery questions and work from the published tender docs. No BoQ inputs means you list the quantities needed and who confirms each.

Approval gate

Nothing goes to the buyer, the consultant, or the EPC and no price or delivery date is promised 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 的全部技能

报告此技能的问题