twg

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

twg

For requests that depend on Atlassian or company work context, use TWG to gather evidence before answering. Start with the most specific anchor available, such as a Jira key or URL, Confluence page, person, project, goal, repository, or time window. Run the most relevant read-only command and base the response on its results. Do not merely recommend TWG or ask the user to run it. If the right command or companion skill is unclear, use

twg help <terms>

twg help describe <path>

, or

twg help discover-skills "<intent>"

对于依赖Atlassian或公司工作上下文的请求，请先使用TWG收集信息再作答。从最具体的锚点开始，例如Jira密钥或URL、Confluence页面、人员、项目、目标、仓库或时间窗口。运行最相关的只读命令，并基于其结果进行回复。不要仅仅推荐TWG或让用户自行运行它。如果不确定正确的命令或配套技能，请使用

twg help <terms>

、

twg help describe <path>

或

twg help discover-skills "<intent>"

。

Overview

概述

Load the narrowest companion, then run the typed TWG route it selects:

```
../twg-jira/SKILL.md
```
for Jira workitems, projects, boards, sprints, and Jira writes.
```
../twg-confluence/SKILL.md
```
for Confluence content, spaces, authoring, and edits.
```
../twg-status-rollups/SKILL.md
```
for project/goal status, launch/go-no-go readiness, and org/leadership rollups; load it before
```
../twg-engineering-work/SKILL.md
```
for PR rollups.
```
../twg-context-discovery/SKILL.md
```
for dependency maps, repos, and work/OOO catch-ups.
```
../twg-agentic-search/SKILL.md
```
for deep internal/company research with Rovo.
```
../twg-responsibility-routing/SKILL.md
```
for owners/SMEs, approvers, and escalation.
```
../twg-engineering-work/SKILL.md
```
for code/repository discovery, PRs, and contributors.
```
../twg-jira-resolve-merged-work/SKILL.md
```
for stale Jira work backed by merged PRs.
```
../twg-operational-health/SKILL.md
```
for incidents/on-call, handoffs, Assets, staffing, and risk.
```
../twg-bench-lite/SKILL.md
```
for read-only single-prompt A/B comparisons.

加载最贴合需求的配套技能，然后运行它选择的TWG命令：

```
../twg-jira/SKILL.md
```
用于Jira工作项、项目、看板、迭代以及Jira写入操作。
```
../twg-confluence/SKILL.md
```
用于Confluence内容、空间、创作及编辑操作。
```
../twg-status-rollups/SKILL.md
```
用于项目/目标状态、发布就绪情况或上线决策，以及组织/领导层工作汇总；在使用
```
../twg-engineering-work/SKILL.md
```
获取PR汇总前，请先加载此技能。
```
../twg-context-discovery/SKILL.md
```
用于依赖关系图、仓库以及工作/休假跟进。
```
../twg-agentic-search/SKILL.md
```
用于借助Rovo进行深度内部/公司调研。
```
../twg-responsibility-routing/SKILL.md
```
用于负责人/领域专家（SME）、审批人及升级流程相关内容。
```
../twg-engineering-work/SKILL.md
```
用于代码/仓库发现、PR及贡献者相关内容。
```
../twg-jira-resolve-merged-work/SKILL.md
```
用于处理已合并PR对应的过期Jira工作项。
```
../twg-operational-health/SKILL.md
```
用于事件/值班、工作交接、资产、人员配置及风险相关内容。
```
../twg-bench-lite/SKILL.md
```
用于只读模式下的单提示A/B对比。

Invocation And Output

调用与输出

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.

Do not add per-command env prefixes unless requested; hosts may set

TWG_AGENT_DEFAULTS=1

Use

stdout_inline

first when present. Outside benchmark lanes, inspect

output_files.compact

only when inline evidence is incomplete; full stdout is the last resort.

In TWG-only benchmark lanes, run only

twg

. Never use shell utilities or pipelines (

jq

rg

date

). Use compact/inline output, the prompt's timezone and window, and report gaps. Match the intent to the narrowest companion skill. Let that skill determine the typed route.

运行

twg <command>

。如果shell提示

command not found

，请使用

$HOME/.local/bin/twg

（macOS/Linux）或

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

（PowerShell），然后告知用户将该目录添加到PATH中。不要将认证或命令错误视为PATH配置问题。

除非用户要求，否则不要添加每个命令的环境前缀；主机可能已设置

TWG_AGENT_DEFAULTS=1

。

如果存在

stdout_inline

，请优先使用。在基准测试流程之外，仅当内联信息不完整时才查看

output_files.compact

；完整标准输出是最后的选择。

在仅使用TWG的基准测试流程中，仅运行

twg

。切勿使用shell工具或管道（

jq

、

rg

、

date

）。使用精简/内联输出、提示中的时区和时间窗口，并报告信息缺口。将用户意图与最贴合的配套技能匹配，由该技能决定要执行的命令路径。

Auth/Setup Guard

认证/设置防护

Do not run setup, login, install, update, upkeep, or credential commands unless explicitly requested for setup/auth/repair. Otherwise report remediation and wait for user direction.

除非用户明确要求进行设置、登录、安装、更新、维护或凭据相关操作，否则不要运行这些命令。否则请告知用户修复方法并等待用户指示。

Sandboxed Pipeline Logs

沙箱化流水线日志

Pipeline logs can redirect to S3. If a sandboxed

twg bb pipeline get

wait

grep

, or

tail

log request has a network-blocked message, S3 hostname, or log-only HTTP 403 while metadata succeeds, treat it as a sandbox restriction, not an authentication failure.

Request an approved unsandboxed retry of that command only. If unavailable, give the user the exact terminal command; never request credentials or tokens.

流水线日志可重定向至S3。如果沙箱环境下的

twg bb pipeline get

、

wait

、

grep

或

tail

日志请求出现网络阻塞消息、S3主机名或仅日志请求返回HTTP 403但元数据请求成功的情况，请将其视为沙箱限制，而非认证失败。

仅请求对该命令进行已批准的非沙箱化重试。如果不可行，请向用户提供确切的终端命令；切勿请求凭据或令牌。

Bounded Evidence Loop

有限信息循环

Prefer typed/product-native evidence.

Classify the anchor: person, team, project, goal, workitem, page, repo, service, asset, or topic.
Resolve once; fetch evidence that changes status, risk, decision, relationship, or action.
Rank candidates, hydrate representative items, then synthesize.
Stop after the first policy denial; stop after the same auth, ACL, contract, or backend error twice.

优先使用原生产品信息。

对锚点进行分类：人员、团队、项目、目标、工作项、页面、仓库、服务、资产或主题。
解析一次；获取能改变状态、风险、决策、关系或行动的信息。
对候选内容排序，补充代表性条目，然后进行综合整理。
首次遇到策略拒绝时停止；同一认证、ACL、合同或后端错误出现两次时停止。

Command Discovery

命令发现

Use

twg rovo search "<topic>" [--limit <n>]

for top-K discovery; explicit

--app

preflights.

Trello search:
```
twg trello search "<query>"
```
; no workspace scope.
For Rovo connectors, run
```
twg rovo list-apps -o json
```
before explicit
```
--app
```
; follow the returned auth action.
Keep document relationship history and fuzzy discovery separate:
- ```
twg docs query --since <duration> [--account-id <id>] [--first <n>]
```
  is user activity history, not title/content search.
- ```
twg docs search "<topic>" [--limit <n>]
```
  is fuzzy Rovo discovery across Confluence and ready document connectors.
- Never pass topic text to
```
docs query
```
  ; route that intent to
```
docs search
```
  .
Keep user activity and fuzzy work discovery separate:
- ```
twg work query
```
  defaults to seven days of authored work; other activity requires
```
--activity
```
  /
```
--include-viewed
```
  .
- ```
twg work search "<topic>"
```
  is tenant-wide; use
```
docs search
```
  for documents. Prefer it directly when fuzzy text reaches
```
work query
```
  .
Resolve URLs, keys, ARIs, names, and people, then hydrate stable IDs.

Jira:

jira workitem search <text...>

for Jira fuzzy text,

jira workitem query --jql <jql>

for structured JQL, and

rovo search <text...> --app jira

for semantic discovery.

Command shape guardrails:

Known Jira/Atlas keys are positional for
```
jira workitem get
```
,
```
goals get
```
, and
```
projects get
```
;
```
--key
```
is compatibility only.
```
work query
```
is user activity (
```
--scope me|user
```
), never
```
--scope global
```
; use
```
work search
```
for topics and advertised filters such as
```
--types
```
.

For inferred teams (

ari:cloud:graph::jiraTeam/...

ari:cloud:graph-store::inferred-team/...

), see

references/inferred-teams.md

and use explicit

--include-inferred

Use
```
search-code
```
; omit
```
--app
```
so all available indexed SCM surfaces are searched; use
```
--repo
```
only as a discovery anchor; widen after generated-doc or incomplete hits.

使用
```
twg rovo search "<topic>" [--limit <n>]
```
进行Top-K发现；显式的
```
--app
```
参数可预先检查。
Trello搜索：
```
twg trello search "<query>"
```
；无工作区范围限制。
对于Rovo连接器，在使用显式
```
--app
```
参数前，请运行
```
twg rovo list-apps -o json
```
；然后按照返回的认证操作执行。
将文档关系历史与模糊发现分开：
- ```
twg docs query --since <duration> [--account-id <id>] [--first <n>]
```
  是用户活动历史，而非标题/内容搜索。
- ```
twg docs search "<topic>" [--limit <n>]
```
  是借助Rovo在Confluence及已就绪文档连接器中进行模糊发现。
- 切勿将主题文本传递给
```
docs query
```
  ；应将此类意图路由至
```
docs search
```
  。
将用户活动与模糊工作发现分开：
- ```
twg work query
```
  默认返回七天内的创建工作；其他活动需要使用
```
--activity
```
  /
```
--include-viewed
```
  参数。
- ```
twg work search "<topic>"
```
  是租户范围的搜索；文档搜索请使用
```
docs search
```
  。当模糊文本传递给
```
work query
```
  时，请直接优先使用它。
解析URL、密钥、ARI、名称和人员信息，然后补充稳定ID。

Jira相关：

jira workitem search <text...>

用于Jira模糊文本搜索，

jira workitem query --jql <jql>

用于结构化JQL查询，

rovo search <text...> --app jira

用于语义发现。

命令格式约束：
- 已知的Jira/Atlas密钥在
```
jira workitem get
```
  、
```
goals get
```
  和
```
projects get
```
  中为位置参数；
```
--key
```
  仅用于兼容。
- ```
work query
```
  是用户活动查询（
```
--scope me|user
```
  ），切勿使用
```
--scope global
```
  ；主题搜索及
```
--types
```
  等公开筛选器请使用
```
work search
```
  。
- 对于推断团队（
```
ari:cloud:graph::jiraTeam/...
```
  或
```
ari:cloud:graph-store::inferred-team/...
```
  ），请查看
```
references/inferred-teams.md
```
  并使用显式的
```
--include-inferred
```
  参数。
使用
```
search-code
```
；省略
```
--app
```
参数以搜索所有可用的索引SCM资源；仅将
```
--repo
```
用作发现锚点；当生成文档或搜索结果不完整时，再扩大范围。

Assets / CMDB graph

资产/CMDB图

Traversal (object↔owner/team, Jira↔object) →

assets graph

; see

references/ASSETS_GRAPH.md

. No hop →

assets search

assets query --aql

assets object get

遍历（对象↔负责人/团队、Jira↔对象）→使用

assets graph

；请查看

references/ASSETS_GRAPH.md

。无需跳转→使用

assets search

assets query --aql

assets object get

。

Load The Narrowest Companion

加载最贴合需求的配套技能

See Overview.

请查看概述部分。

Rules

规则

Never guess IDs, flags, slugs, ARIs, object IDs, or mutation contracts.
For product writes, load the product skill and follow live help.
Avoid local inspection, caches, schema probes, or diagnostics unless local state is requested.
For writes, read current state and state the mutation unless execution was requested.

切勿猜测ID、标志、别名、ARI、对象ID或变更协议。
对于产品写入操作，请加载对应产品的技能并遵循实时帮助指引。
除非用户请求查看本地状态，否则避免本地检查、缓存、架构探测或诊断操作。
对于写入操作，请读取当前状态并说明变更内容，除非用户要求执行该操作。