twg-status-rollups

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

twg-status-rollups

Use with the root

twg

skill. Get exact command grammar from live

twg help

twg help <terms>

, or

twg help describe <path>

与根技能

twg

配合使用。可通过实时

twg help

、

twg help <terms>

或

twg help describe <path>

获取准确的命令语法。

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配置问题。

Use When

使用场景

"What did I/person/team/org work on?" or weekly personal update
Short-window personal update, standup, handoff, or restart after time away
"Status of project/goal/topic/focus area"
"Is this project ready to launch?" or go/no-go decision brief
Leadership, monthly, annual, cycle, appraisal, or goal-alignment readout
Org bottlenecks, priorities, stale goals, or project risks

查询“我/某人/团队/组织完成了哪些工作？”或撰写每周个人更新
短周期个人更新、站会发言、工作交接，或休假后复工梳理
查询“项目/目标/主题/重点领域的状态”
判断“该项目是否准备好上线？”或提供上线/不上线决策简报
面向领导层的月度、年度、周期汇报，绩效评估或目标对齐报告
识别组织瓶颈、优先级、停滞目标或项目风险

First Move

第一步操作

Resolve scope before retrieval:

Person/team/org: resolve identity, roster, or org-tree groups.
Project, goal, focus area, or topic: resolve native key, ARI, URL, name, or central project/page/workitem anchors.

Establish the time window. If absent, ask when precision matters; otherwise use a recent bounded window and state it. Keep personal summaries to 1 year or less.

在获取数据前先明确范围：

人员/团队/组织：确认身份、人员名单或org-tree分组。
项目、目标、重点领域或主题：确认原生标识、ARI、URL、名称，或核心项目/页面/工作项锚点。

确定时间范围。若用户未指定，当需要精确结果时请询问用户；否则使用近期的固定时间范围并明确说明。个人总结的时间范围请控制在1年以内。

Tree Routing Matrix

树路由矩阵

```
pr-tree
```
: merged/open PRs, reviews, shipped work, or repo momentum by manager or team. Default for PR-constrained evidence.
```
org-tree
```
: manager chain, roster, and reporting structure; use for grouping, not delivery evidence.
```
workitem-tree
```
: Jira issue load and active/done movement by org tree.
```
work-tree
```
: multi-surface org counts across Jira, PRs, goals, projects, docs, or videos. Not for PR-only or Jira-only asks.

```
pr-tree
```
：按经理或团队统计已合并/待合并PR、评审情况、已交付工作或仓库进展。适用于以PR为核心依据的场景。
```
org-tree
```
：展示经理汇报链、人员名单和汇报结构；用于分组管理，而非交付成果依据。
```
workitem-tree
```
：按组织树统计Jira任务负载及活跃/已完成任务的流转情况。
```
work-tree
```
：跨Jira、PR、目标、项目、文档或视频多维度统计组织数据。不适用于仅需PR或仅需Jira数据的查询。

Fast Path: PR-Based Leadership Rollup

快速路径：基于PR的领导层汇总

For PR-based leadership prompts:

Preserve the requested scope and window; for "last 2 weeks," use
```
--since 14d
```
.
Use
```
pr-tree
```
first. It groups by reporting-tree
```
directReports
```
; add
```
org-tree
```
only for hierarchy context.
If option shape is uncertain, inspect
```
twg help describe "pr-tree"
```
before the data call; do not probe incompatible flag combinations.
Start count-first, then make at most one supported sampling/full-fetch pass for repo or theme evidence. Synthesize at manager/team level from that tree. Do not issue per-person queries merely to populate every group; use one targeted PR follow-up only when a material theme lacks representative proof.
Add one secondary surface only for a named gap.

Target 2-4 calls.

针对基于PR的领导层汇报需求：

保留用户请求的范围和时间窗口；例如“过去2周”对应使用
```
--since 14d
```
参数。
优先使用
```
pr-tree
```
。它按汇报树的
```
directReports
```
分组；仅当需要层级上下文时才添加
```
org-tree
```
。
若不确定参数格式，请在调用数据前查看
```
twg help describe "pr-tree"
```
；请勿尝试不兼容的参数组合。
先统计数量，然后最多执行一次支持的抽样/全量获取操作，以获取仓库或主题相关依据。基于该树在经理/团队层面进行汇总。请勿仅为填充每个分组而发起针对个人的查询；仅当某个重要主题缺乏代表性依据时，才进行一次针对性的PR跟进查询。
仅当存在明确的数据缺口时，才添加一个次要数据来源。

目标调用次数为2-4次。

Evidence Policy

证据原则

Match evidence to prompt constraints; merged-PR-only conclusions require PR evidence.
Start count-first on tree surfaces; hydrate examples only for themes, risks, or owner attribution.
Rank broad lists before minimal hydration.
Distinguish authored delivery from review, coordination, and influence.
Stop when evidence is sufficient. After two identical backend failures, stop that path and report the gap.

证据需符合请求约束；仅基于已合并PR的结论必须使用PR作为证据。
在树状数据源上先统计数量；仅针对主题、风险或归属者补充具体示例。
先对广泛列表进行排序，再补充少量具体内容。
区分交付工作、评审工作、协调工作和影响力贡献。
当证据足够时停止操作。若同一后端连续失败两次，请停止该路径并报告数据缺口。

Recipe Cards

方案模板

Person Or Personal Update

个人或个人工作更新

Resolve the person, then pull recent Jira work, PRs, docs/pages, meetings, and project/goal involvement. Load

references/personal-work-summary.md

for exact subject, notification, PR hydration, and outcome-first rules. Separate delivery, review, docs/strategy, coordination, and influence.

确认人员身份，然后获取近期Jira工作、PR、文档/页面、会议记录，以及参与的项目/目标信息。加载

references/personal-work-summary.md

以获取关于主题、通知、PR详情及成果优先原则的具体规则。区分交付、评审、文档/策略、协调和影响力贡献。

Short-Window Personal Update / Standup

短周期个人更新/站会

Load

references/personal-work-summary.md

. Resolve the person, preserve the requested project and window, prioritize material work, and distinguish evidence gaps from confirmed blockers.

加载

references/personal-work-summary.md

。确认人员身份，保留用户请求的项目和时间窗口，优先展示重要工作，区分证据缺口与已确认的阻塞问题。

Team Or Org Leadership Readout

团队或组织领导层汇报

Resolve org-tree first. Org projects:

twg projects query --scope org --include-inferred

(

[Paid: Intelligence]

). Group results; hydrate outliers affecting momentum, blockers, or ownership.

优先确认org-tree。组织项目：使用

twg projects query --scope org --include-inferred

（[付费功能：智能分析]）。对结果进行分组，补充影响进展、阻塞问题或归属情况的异常数据。

Project Or Goal Status

项目或目标状态

Fetch the native project/goal first. Include owner, state, update, links, dates, and recency. Hydrate only risk, progress, or dependency evidence.

优先获取原生项目/目标信息。包含负责人、状态、更新内容、链接、日期和最新更新时间。仅补充风险、进度或依赖相关证据。

Decision Readiness / Go-No-Go

决策就绪/上线/不上线判断

Load

references/decision-readiness.md

. Resolve the native project or decision anchor first and keep explicit links as the scope boundary. Identify the gates, then give the requested decision or recommendation with confidence, gaps, and change conditions. Do not infer owners.

加载

references/decision-readiness.md

。优先确认原生项目或决策锚点，并将明确的链接作为范围边界。识别决策关卡，然后给出符合请求的决策或建议，并说明置信度、数据缺口和变更条件。请勿推断负责人。

Topic Status

主题状态

Resolve/search once, select central project, goal, page, or workitem anchors, then hydrate those before using broad work/activity queries.

先进行一次解析/搜索，选择核心项目、目标、页面或工作项锚点，然后补充这些锚点的信息，再使用广泛的工作/活动查询。

References

参考资料

```
references/personal-work-summary.md
```
- standups, catch-ups, and broader personal status evidence
```
references/decision-readiness.md
```
- cross-domain go/no-go and approval evidence

```
references/personal-work-summary.md
```
- 站会、复盘及更广泛的个人状态依据
```
references/decision-readiness.md
```
- 跨领域上线/不上线及审批依据

Appraisal / Performance Evidence

绩效评估/绩效证据

Resolve person and horizon. Separate delivery, review, collaboration, docs/strategy, project/goal impact, and stakeholder signals. Avoid count-only ranking; add caveats when evidence is weak.

确认人员身份和时间范围。区分交付、评审、协作、文档/策略、项目/目标影响和利益相关方反馈。避免仅依赖数量排序；当证据不足时需添加说明。

Output Shape

输出格式

Executive summary first, with 3-6 high-signal observations.
Table with owner/team/workstream, positive signals, risk signals, current focus, confidence, and evidence.
Risks and leadership attention ranked by impact and owner.
Confidence and gaps, including stale updates, missing product coverage, ACL gaps, or sampled evidence boundaries.

先展示执行摘要，包含3-6个高价值观察结论。
表格包含负责人/团队/工作流、积极信号、风险信号、当前重点、置信度和证据。
按影响程度和负责人排序风险及需领导层关注的事项。
说明置信度和数据缺口，包括过时更新、缺失产品覆盖、ACL权限缺口或抽样证据边界。

Anti-Patterns

反模式

Do not make a status report a list of every artifact.
Do not infer goal/project health from issue counts alone.
Do not fan out across every org member if manager/team-level grouping answers the prompt.
Do not use search snippets as final evidence for status or risk.
Start explicit merged/open PR rollups with
```
pr-tree
```
, not the other trees.

请勿将状态报告做成所有工件的清单。
请勿仅根据任务数量推断目标/项目健康状况。
若经理/团队层面的分组已能满足请求，请勿针对每个组织成员发起查询。
请勿将搜索片段作为状态或风险的最终证据。
明确的已合并/待合并PR汇总请从
```
pr-tree
```
开始，而非其他树状数据源。