gtm-icp

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

GTM ICP

Trigger

触发条件

Apply this Lifecycle SOP when the requested outcome creates, updates, repairs, or retires an ideal customer profile owned by an organization node in an existing GTM workspace.

当请求的目标是在现有GTM工作区中创建、更新、修复或停用由组织节点拥有的ICP（理想客户画像）时，应用此生命周期SOP。

Scope

适用范围

Own node-local, freeform Markdown ICPs at

icps/<icp-slug>/ICP.md

across creation, refinement, deletion, and repo-wide ICP integrity repair. Create and fully research ICPs with the shared company-data contract, interpreted as desired or accepted account criteria. Read legacy

icps/<icp-slug>.md

artifacts without requiring migration. Do not author persona or member files, manage the workspace lifecycle, or classify/research accounts against saved ICPs.

Contract

Field	Public contract
Reads	Accepted ICP facts and uncertainty, the root-to-owner `ORG.md` chain, owner-local ICPs, and safe supplied sources
Writes	Only the selected owner's canonical ICP path, or scoped ICP repairs during doctor
Outputs	An accepted node-owned ICP identified by display name and owner chain, a complete health report, or a scoped handoff
Approval	The agent prepares, stages, inspects, and commits the scoped change locally, then the user approves one plain-language card immediately before the push
Persists	Accepted ICP files in `main` Git history; no hidden coordination state
Handoff	`gtm-workspace` for repository structure or connections, `gtm-persona` for buyers, and `gtm-workflow` for saved operational work

负责管理路径为

icps/<icp-slug>/ICP.md

的节点本地、自由格式Markdown类型ICP，涵盖创建、优化、删除以及全仓库范围的ICP完整性修复。使用共享的公司数据合约创建并全面调研ICP，将其解读为期望或可接受的客户标准。支持读取旧版

icps/<icp-slug>.md

产物，无需进行迁移。不负责编写用户画像（persona）或成员文件、管理工作区生命周期，也不根据已保存的ICP对客户进行分类或调研。

合约

字段	公共约定
读取内容	已确认的ICP事实与不确定性、从根节点到所属节点的 `ORG.md` 链路、所属节点本地ICP，以及安全的外部提供来源
写入范围	仅写入所选所属方的规范ICP路径，或在修复（doctor）操作中进行限定范围的ICP修复
输出内容	经确认的、由节点拥有的ICP（通过显示名称和所属链路标识）、完整的健康报告，或限定范围的交接
审批流程	Agent在本地准备、暂存、检查并提交限定范围的变更，然后用户在推送前立即对一张简明变更卡片进行审批
持久化方式	已确认的ICP文件存储于 `main` 分支的Git历史中；无隐藏的协调状态
交接对象	仓库结构或连接问题交接给 `gtm-workspace` ，买家相关问题交接给 `gtm-persona` ，已保存的运营工作问题交接给 `gtm-workflow`

Inputs

输入项

Use the user's accepted ICP facts and uncertainty, the hosting environment's connected-repo and durable-write declarations, the root-to-owner

ORG.md

chain, owner-local ICPs, and safe supplied sources.

使用用户确认的ICP事实与不确定性、宿主环境的已连接仓库与持久化写入声明、从根节点到所属节点的

ORG.md

链路、所属节点本地ICP，以及安全的外部提供来源。

Roles

角色职责

The agent owns the selected ICP lifecycle flow. The user approves one plain-language card immediately before the push that saves the prepared local commit.

gtm-workspace

owns repository structure and connections.

Agent负责所选ICP的生命周期流程。用户在推送（用于保存已准备的本地提交）前立即对一张简明变更卡片进行审批。

gtm-workspace

负责仓库结构与连接管理。

Procedure

操作流程

Condition	Owned flow
The requested outcome belongs to a sibling workflow	Hand off before workspace resolution or artifact reads; mutate nothing
No lifecycle verb is clear	Guide the ICP lifecycle menu and retain ownership of the selected flow
Create or define is requested	Resolve the workspace and owner node, ground one or many factual drafts, check owner-local overlap, describe them, and save the accepted ICPs together
Update or refine is requested	Resolve one visible ICP, preserve unrelated facts, describe the change, and save the accepted revision
Delete is requested	Resolve one visible ICP, describe ownership and consequences, remove only the accepted target, and say it can be restored on request
Doctor is requested or ICP artifacts seem malformed	Inspect ICP placement and content repo-wide, describe the repair set, save it once, and report resulting health

触发条件	负责流程
请求的目标属于同级工作流	在解析工作区或读取产物前完成交接；不进行任何变更
无明确的生命周期操作动词	引导用户查看ICP生命周期菜单，并保留对所选流程的所有权
请求创建或定义	解析工作区与所属节点，生成一份或多份基于事实的草稿，检查所属节点本地的重复项，描述草稿内容，并统一保存已确认的ICP
请求更新或优化	解析一份可见的ICP，保留无关事实，描述变更内容，并保存已确认的修订版本
请求删除	解析一份可见的ICP，说明所有权与删除后果，仅移除已确认的目标，并告知用户可按需恢复
请求修复或ICP产物存在格式异常	检查全仓库范围内的ICP存放位置与内容，描述修复集合，一次性保存修复内容，并报告最终的健康状态

Outputs

输出项

Produce the accepted node-owned ICP state, identified by display name and owner chain, or a complete ICP health report. A request owned by a sibling workflow produces only a scoped handoff and no artifact mutation.

输出经确认的、由节点拥有的ICP状态（通过显示名称和所属链路标识），或完整的ICP健康报告。若请求属于同级工作流，则仅输出限定范围的交接信息，不进行任何产物变更。

Exceptions

异常处理

If no valid workspace is connected or discoverable, stop without writing and direct workspace creation or connection to

gtm-workspace

. If a required reference is unavailable or the environment cannot durably save the accepted operation, keep the repo unchanged and use the prescribed recovery.

如果没有已连接或可发现的有效工作区，停止操作且不写入任何内容，并引导用户通过

gtm-workspace

创建或连接工作区。如果所需的参考资料不可用，或环境无法持久化保存已确认的操作，则保持仓库不变，并使用规定的恢复流程。

QC

质量控制

Follow the shared interaction standard for every question, proposal, approval, and closing message; ask every missing result-changing fact in one decision message and never use
```
AskUserQuestion
```
.
Preserve every supplied qualification, disqualifier, and uncertainty; organization facts and adjacent ICPs are a factual ceiling, never evidence for invented ICP claims.
Keep all 13 company-data fields in the required order for every new or fully researched
```
ICP.md
```
; write
```
Unknown
```
instead of inventing or dropping unresolved criteria.
Prepare only the requested ICP files locally and never show complete bytes unless asked; the card must describe exactly what the prepared commit changes. Preserve legacy reads and node-local visibility and mutate only ICP paths.
Stage only named ICP paths, inspect the diff, commit locally, then show one card naming what changes and invoke
```
git push
```
with that card as the approval summary. Close a verified push with
```
Saved.
```

所有问题、提案、审批和结束消息都需遵循共享交互标准；所有会影响结果的缺失事实都要在同一条决策消息中询问，且绝不使用
```
AskUserQuestion
```
。
保留所有提供的合格条件、不合格条件和不确定性；组织相关事实和相邻ICP是事实上限，绝不能作为编造ICP声明的依据。
所有新建或经过全面调研的
```
ICP.md
```
都需按要求顺序保留全部13个公司数据字段；未解决的标准写
```
Unknown
```
，不得编造或遗漏。
仅在本地准备请求的ICP文件，除非用户要求，否则绝不展示完整文件内容；变更卡片必须准确描述已准备的提交所包含的变更。保留旧版文件读取能力与节点本地可见性，仅修改ICP路径下的内容。
仅暂存指定的ICP路径，检查差异，在本地提交，然后展示一张说明变更内容的卡片，并以该卡片作为审批摘要执行
```
git push
```
。推送验证通过后以
```
Saved.
```
结束。

References

参考资料

Read the ICP contract for every flow; it defines workspace resolution, ownership, visibility, content, acceptance, safety, and persistence.
Read the shared company-data research contract before creating or fully researching an ICP; apply its ordered fields as desired or accepted account criteria.
Read the ICP lifecycle flows after selecting the Procedure row; they define menu, create, update, delete, doctor, recovery, and closure.
Render the ICP draft template only for create; it is a starting shape, not a schema or validity test.
Read the shared interaction standard before any user-facing message; it defines audience language, length and formatting, proposal shape, batching, decision messages, approval by surface, and closing.

所有流程都需阅读ICP合约；它定义了工作区解析、所有权、可见性、内容、验收、安全性和持久化规则。
创建或全面调研ICP前需阅读共享公司数据调研合约；将其有序字段作为期望或可接受的客户标准应用。
选择操作流程对应的行后，阅读ICP生命周期流程；它定义了菜单、创建、更新、删除、修复、恢复和结束的规则。
仅在创建ICP时使用ICP草稿模板；它是初始框架，而非模式或有效性测试标准。
发送任何面向用户的消息前需阅读共享交互标准；它定义了受众语言、长度与格式、提案形式、批量处理、决策消息、界面审批以及结束规则。