twg-responsibility-routing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

twg-responsibility-routing

—

twg责任路由

Use the root

twg

skill. Use this workflow to answer “who should I involve, why them, and in what role?” Do not assume a broad topic is an exact product.

使用根技能

twg

。通过此工作流解答“我应该联系谁、为什么联系他们，以及他们担任什么角色？”的问题。请勿假设宽泛的主题对应某个具体产品。

CLI launcher fallback

—

CLI启动器备选方案

Run

twg <command>

. On shell

command not found

, use

$HOME/.local/bin/twg

(macOS/Linux) /

$env:LOCALAPPDATA\Programs\twg\bin\twg.exe

(PowerShell), then tell user to add that directory to PATH. Do not treat auth or command errors as PATH failures.

运行

twg <command>

。若shell提示

command not found

，请使用

$HOME/.local/bin/twg

（macOS/Linux系统）或

$env:LOCALAPPDATA\Programs\twg\bin\twg.exe

（PowerShell环境），然后告知用户将该目录添加至PATH。请勿将认证错误或命令错误视为PATH配置问题。

Classify The Role

—

角色分类

Keep these roles distinct:

Declared owner: formally accountable for an entity or area.
Operational owner or maintainer: responsible for current delivery or operation.
Expert: has source-backed depth in one workstream.
Reviewer or consulted party: evaluates or advises but may not decide.
Approver or decision authority: can authorize the specific ask or decision.
Escalation or Head of Engineering contact: leads the responsible engineering organization or can route an unresolved ask.
Informed stakeholder: affected by the decision but not responsible for it.

请明确区分以下角色：

Declared owner（指定负责人）：对某个实体或领域负有正式责任。
Operational owner or maintainer（运营负责人/维护者）：负责当前交付或运营工作。
Expert（专家）：在某一工作流中具备有资料支撑的专业深度。
Reviewer or consulted party（审核者/咨询对象）：负责评估或提供建议，但无决策权。
Approver or decision authority（批准者/决策负责人）：可批准特定需求或决策。
Escalation or Head of Engineering contact（升级对接人/工程主管）：领导相关工程组织，或可对接未解决的需求。
Informed stakeholder（知情干系人）：受决策影响，但无需承担责任。

Resolve Scope Before People

—

先明确范围，再对接人员

For a fuzzy topic or area, compare one bounded

twg rovo search "<topic>" --app confluence

pass with one bounded

twg work search "<topic>"

pass. Group same-named results into distinct initiative, platform, domain, feature, and team clusters. Hydrate 2-5 central charters, roadmaps, services, projects, or active workstreams before ranking people. If the sources disagree, show the alternative scopes or ask the user.

For a stable project, goal, component, service, work item, page, or repository, use that reference directly.

若主题或领域模糊不清，请对比一次限定范围的

twg rovo search "<topic>" --app confluence

搜索结果与一次限定范围的

twg work search "<topic>"

搜索结果。将同名结果归类为不同的倡议、平台、领域、功能和团队集群。在排序人员前，先梳理2-5个核心章程、路线图、服务、项目或活跃工作流。若来源信息不一致，请展示备选范围或询问用户。

对于稳定的项目、目标、组件、服务、工作项、页面或仓库，请直接使用对应的引用。

Find Responsibility And Authority

—

确定责任与权限

Use
```
twg responsibility get <reference>
```
for declared owners, teams, maintainers, approvers, reviewers, or escalation roles.
Use
```
twg responsibility infer <reference>
```
only when declared responsibility is missing or the user asks for evidence-based candidates. Preserve confidence, reason codes, evidence window, and declared-versus-observed status.
Infer primarily from scoped search, declared roles, and hydrated work evidence. Org data is optional; do not block or weaken the workflow merely because it is unavailable.
When org data is connected and a candidate leader or manager is known, prefer the narrowest useful tree:
```
org-tree
```
for hierarchy,
```
work-tree
```
for cross-surface breadth,
```
workitem-tree
```
for Jira work, or
```
pr-tree
```
for PR authorship/review. Tree counts help validate reach and organizational scope; they do not by themselves prove expertise, ownership, or approval authority.
For an approval ask, inspect the artifact that defines the decision: project or goal ownership, Jira workflow/approver fields, charter, decision record, or accountable team. State separately who can recommend, who must be consulted, and who can approve. Never promote an active contributor into an approver.
For escalation, give the nearest verified owner first. Add the engineering leader only when the owner is missing, blocked, cross-team, or the ask needs organizational authority.

Use

twg-context-discovery

only when relationship or dependency expansion is needed after the scope and people roles are established. It is not the default route for a responsibility question.

使用
```
twg responsibility get <reference>
```
查询指定负责人、团队、维护者、批准者、审核者或升级对接角色。
仅当无指定责任信息或用户要求提供基于证据的候选人时，才使用
```
twg responsibility infer <reference>
```
。请保留置信度、原因代码、证据时间范围以及指定状态与实际状态的对比信息。
推断主要基于限定范围的搜索、指定角色和梳理后的工作证据。组织数据为可选信息；请勿因组织数据不可用而中断或弱化工作流。
若已连接组织数据且已知候选领导者或管理者，请优先使用最贴合需求的树状结构：
```
org-tree
```
用于层级关系，
```
work-tree
```
用于跨领域广度，
```
workitem-tree
```
用于Jira工作项，
```
pr-tree
```
用于PR作者/审核信息。树状结构的数量有助于验证覆盖范围和组织规模，但本身无法证明专业能力、所有权或批准权限。
若涉及批准请求，请查看定义决策的相关文件：项目或目标所有权、Jira工作流/批准者字段、章程、决策记录或负责团队。分别说明谁可提出建议、谁必须被咨询、谁可批准。切勿将活跃贡献者直接认定为批准者。
对于升级请求，优先提供最近的已验证负责人。仅当负责人缺失、受阻、涉及跨团队或请求需要组织级权限时，才添加工程主管。

仅当已明确范围和人员角色后，需要扩展关系或依赖时，才使用

twg-context-discovery

。它并非责任类问题的默认处理路径。

Evidence And Output

—

证据与输出

Strong evidence includes explicit ownership, accountable roles, workflow authority, charter/roadmap leadership, service ownership, sustained decisions, or repeated central contributions. Profile text, org proximity, one document, raw activity, or a self-authored update is weak evidence by itself.

For topic/SME maps, return at most five workstreams and one primary expert per workstream unless the user asks for more. Name an overall owner only with cross-workstream evidence. For approval or escalation asks, return the proposed contact, role, scope, evidence, confidence, why they are appropriate, and a suggested question or reach-out. State when authority is unconfirmed.

Stop when another search would not change scope, role, authority, escalation, confidence, or the recommended contact.

强有力的证据包括明确的所有权、责任角色、工作流权限、章程/路线图领导权、服务所有权、持续决策或多次核心贡献。个人简介文本、组织关联度、单份文档、原始活动记录或自行更新的信息本身属于较弱的证据。

对于主题/专家映射，除非用户要求更多结果，否则最多返回5个工作流，每个工作流对应1名主要专家。仅当有跨工作流的证据时，才可指定总负责人。对于批准或升级请求，请返回建议对接人、角色、范围、证据、置信度、适配原因以及建议的提问或沟通内容。若权限未确认，请明确说明。

当进一步搜索不会改变范围、角色、权限、升级路径、置信度或建议对接人时，即可停止操作。