gtm-workspace

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

GTM Workspace

GTM 工作区

Trigger

触发条件

Apply this Lifecycle SOP when the requested outcome creates, imports, maintains, validates, repairs, or retires the GTM workspace itself.

当请求的结果涉及创建、导入、维护、验证、修复或停用 GTM 工作区本身时，应用此生命周期 SOP。

Scope

适用范围

Own the plain-Markdown workspace at

~/.gtm/<org-slug>/

across creation, import, organization and member maintenance, legacy-shape migration, structural or Git repair, and deletion. Create and fully research

ORG.md

artifacts with the shared company-data contract and

MEMBER.md

artifacts with the shared person-data contract. Preserve node-owned ICP and persona artifacts without authoring or validating their contents.

Contract

Field	Public contract
Reads	The user's accepted organization facts, repository connection rules, valid local workspaces, and safe supplied sources
Writes	Workspace contract files, organization nodes, member files, repository configuration, and accepted structural repairs
Outputs	The requested workspace state summarized by display name and owner chain, a complete health report, or a fixed-connection refusal
Approval	The agent prepares, stages, inspects, and commits locally, then the user approves one plain-language card immediately before the push; whole-workspace deletion keeps its typed confirmation
Persists	Accepted workspace files and configuration in `main` Git history; no hidden coordination state
Handoff	`gtm-icp` for market definitions, `gtm-persona` for buyer definitions, and `gtm-workflow` for saved workflows

负责管理路径为

~/.gtm/<org-slug>/

的纯 Markdown 工作区，涵盖创建、导入、组织与成员维护、旧格式迁移、结构或 Git 修复以及删除全流程。依据共享的公司数据合约创建并全面调研

ORG.md

产物，依据共享的人员数据合约创建并全面调研

MEMBER.md

产物。保留节点所属的 ICP 和 Persona 产物，不创作或验证其内容。

合约说明

字段	公开合约内容
读取内容	用户已确认的组织信息、仓库连接规则、有效的本地工作区以及安全的提供来源
写入内容	工作区合约文件、组织节点、成员文件、仓库配置以及已确认的结构修复
输出内容	按显示名称和所有者链汇总的请求工作区状态、完整的健康报告，或固定连接拒绝通知
审批流程	Agent 在本地完成准备、暂存、检查和提交，然后用户在推送前立即审批一张简明语言卡片；整个工作区删除操作需保留键入式确认
持久化内容	已确认的工作区文件和配置存储在 `main` Git 历史中；无隐藏协调状态
交接对象	市场定义交由 `gtm-icp` 处理，买家定义交由 `gtm-persona` 处理，已保存工作流交由 `gtm-workflow` 处理

Inputs

输入项

Use the user's request and accepted facts, the hosting environment's repo connection and durable-write declarations, valid local workspaces, and safe supplied sources.

使用用户的请求和已确认的事实、宿主环境的仓库连接和持久化写入声明、有效的本地工作区以及安全的提供来源。

Roles

角色职责

The agent owns the selected lifecycle flow. The user approves one plain-language card immediately before the push that saves the prepared local commit; whole-workspace deletion keeps its typed confirmation. The hosting environment declares fixed connections.

Agent 负责所选的生命周期流程。用户在推送（保存已准备的本地提交）前立即审批一张简明语言卡片；整个工作区删除操作需保留键入式确认。宿主环境负责声明固定连接。

Procedure

操作流程

Condition	Owned flow
A fixed-connection deployment receives import, sharing setup, whole-workspace deletion, a create for a repo other than the connected one, or another connection-changing request	Refuse and redirect through the surface-refusal flow; perform nothing for that request
Create is requested on a fixed-connection deployment whose connected repo has no root `ORG.md` or legacy `org.md`	Guide the create flow with its connected-repo substitutions; the first saved change writes `ORG.md` together with the contract files
No lifecycle verb is clear	Guide the lifecycle menu and retain ownership of the selected flow
Create is requested	Send one intake decision message, research every supplied source, prepare one local commit for the organization and every supplied suborganization and member, show one card, push once on approval, then close
Import is requested	Guide a local copy or GitHub clone through inventory, accepted conversion, history, optional sharing, and summary
Update is requested	Resolve the target, describe the changed facts, save the accepted changes, and close
Delete is requested	Resolve the target, describe consequences, obtain the required confirmation, delete, and explain recovery where available
Doctor or migration is requested, or the workspace seems wrong	Run every contract, legacy-shape, and Git check; describe accepted repairs or migrations; save one change set; and report complete health

条件	负责流程
固定连接部署收到导入、共享设置、整个工作区删除、针对非连接仓库的创建请求，或其他更改连接的请求	通过表层拒绝流程拒绝并重定向；不对该请求执行任何操作
在固定连接部署上请求创建，且其连接的仓库根目录下没有 `ORG.md` 或旧版 `org.md`	使用连接仓库的替代方案引导创建流程；第一次保存的更改会将 `ORG.md` 与合约文件一起写入
无明确的生命周期操作动词	引导至生命周期菜单，并保留对所选流程的所有权
收到创建请求	发送一条准入决策消息，调研所有提供的来源，为组织及所有提供的子组织和成员准备一次本地提交，展示一张卡片，获批后推送一次，然后关闭
收到导入请求	引导本地复制或 GitHub 克隆流程，涵盖清单清点、已确认转换、历史记录、可选共享和总结
收到更新请求	确定目标，描述变更的信息，保存已确认的变更，然后关闭
收到删除请求	确定目标，描述后果，获取所需的确认，执行删除，并说明可用的恢复方式
收到 doctor 或迁移请求，或工作区看起来有问题	运行所有合约、旧格式和 Git 检查；描述已确认的修复或迁移；保存一个变更集；并报告完整健康状况

Outputs

输出项

Produce the requested workspace state and a plain-language summary by display name and owner chain, or a complete health report for doctor. A refused fixed-connection operation produces only the prescribed explanation and CLI redirect; a connected repo that is not set up yet is created in place, not refused.

生成请求的工作区状态，以及按显示名称和所有者链整理的简明语言总结，或针对 doctor 的完整健康报告。被拒绝的固定连接操作仅生成规定的说明和 CLI 重定向；尚未设置的连接仓库将就地创建，而非拒绝。

Exceptions

异常处理

If a required reference is unavailable, use

templates/AGENTS.md

as the minimum contract, keep every member under its owning organization node at

members/<member-slug>/MEMBER.md

, and stay on

main

. If the environment cannot push the prepared commit after approval, stop and offer the prescribed CLI recovery; never report it as saved.

如果所需的参考文档不可用，使用

templates/AGENTS.md

作为最低合约，将所有成员保留在其所属组织节点下的

members/<member-slug>/MEMBER.md

路径中，并保持在

main

分支上。如果环境在获批后无法推送已准备的提交，停止操作并提供规定的 CLI 恢复方案；绝对不要将其报告为已保存。

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
```
.
Prepare only the requested workspace action locally and never show complete bytes unless asked; the card must describe exactly what the prepared commit changes. Name GitHub, the repository, or the folder only in import, sharing setup, whole-workspace deletion, and git-problem recovery; keep branch, remote, upstream, and command details internal unless a problem requires them or the user asks.
Keep all 13 company-data fields in the required order for every new or fully researched
```
ORG.md
```
; preserve uncertainty and write
```
Unknown
```
instead of inventing or dropping unresolved facts.
Keep all eight person-data fields in the required order for every new or fully researched
```
MEMBER.md
```
; retain the required supplied email outside that contract, preserve uncertainty, and write
```
Unknown
```
instead of inventing or dropping unresolved facts.
Stage only named 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.
```
Close only after every selected-flow completion criterion in
```
references/flows.md
```
is satisfied.

所有问题、提案、审批和关闭消息都遵循共享交互标准；在一条决策消息中询问所有缺失的、会影响结果的信息，绝对不要使用
```
AskUserQuestion
```
。
仅在本地准备请求的工作区操作，除非被要求，否则绝不展示完整字节内容；卡片必须准确描述已准备提交的变更内容。仅在导入、共享设置、整个工作区删除和 Git 问题恢复时提及 GitHub、仓库或文件夹；除非问题需要或用户询问，否则分支、远程仓库、上游和命令细节均保持内部可见。
对于每个新建或全面调研的
```
ORG.md
```
，所有 13 个公司数据字段都需按要求顺序排列；保留不确定性，写入
```
Unknown
```
而非编造或遗漏未解决的信息。
对于每个新建或全面调研的
```
MEMBER.md
```
，所有 8 个人员数据字段都需按要求顺序排列；在合约之外保留所需的提供邮箱，保留不确定性，写入
```
Unknown
```
而非编造或遗漏未解决的信息。
仅暂存指定路径，检查差异，本地提交，然后展示一张说明变更内容的卡片，并调用
```
git push
```
，将该卡片作为审批摘要。验证推送成功后，以
```
Saved.
```
关闭。
仅在
```
references/flows.md
```
中所有所选流程的完成标准都满足后，才关闭流程。

References

参考文档

Read the workspace contract for every flow; it defines storage, content, link safety, doctor checks, and persistence.
Read the company-data research contract before creating or fully researching an
```
ORG.md
```
; it defines the ordered fields, value shapes, uncertainty rules, and shared ICP semantics.
Read the person-data research contract before creating or fully researching a
```
MEMBER.md
```
; it defines the ordered fields, value shapes, uncertainty rules, supplied-email boundary, and shared persona semantics.
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.
Read the guided flows after selecting the Procedure row; it defines intake, proposals, recovery, and closure.
Render templates when creating or restoring contract files, replacing placeholders and omitting empty optional fields or sections.

所有流程都需阅读工作区合约；它定义了存储、内容、链接安全、doctor 检查和持久化规则。
在创建或全面调研
```
ORG.md
```
之前，阅读公司数据调研合约；它定义了字段顺序、值格式、不确定性规则和共享 ICP 语义。
在创建或全面调研
```
MEMBER.md
```
之前，阅读人员数据调研合约；它定义了字段顺序、值格式、不确定性规则、提供邮箱边界和共享 Persona 语义。
在发送任何面向用户的消息之前，阅读共享交互标准；它定义了受众语言、长度和格式、提案形式、批量处理、决策消息、表层审批和关闭规则。
选择操作流程中的行之后，阅读引导式流程；它定义了准入、提案、恢复和关闭规则。
创建或恢复合约文件时，使用templates目录下的模板，替换占位符，省略空的可选字段或章节。