rhdh-jira-refine

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Refine RHDH Jira work

优化RHDH Jira工作项

Answer "is this ready" with the criteria the RHDH workflow actually enforces, and say what is missing rather than guessing at it.

根据RHDH工作流实际执行的标准回答“是否就绪”，明确指出缺失内容而非猜测。

Route

流程

Load

workflows/refine-issues.md

. It covers both the per-issue readiness audit and the Feature Exploration checklist — the same checks, applied at different points in a Feature's life.

加载

workflows/refine-issues.md

。该文档涵盖单问题就绪审核和Feature Exploration检查清单——相同的检查项，应用于Feature生命周期的不同阶段。

Not gated on grilling

不依赖grilling技能

Unlike

/rhdh-jira-create

, this skill does not require the external

grilling

skill and must not be blocked on it. Refinement reads work that already exists. Gating it on an optional external skill would take a whole capability offline for no benefit.

与

/rhdh-jira-create

不同，本技能不需要外部

grilling

技能，也不得受其阻塞。优化操作仅读取已存在的工作项。将其依赖于可选外部技能会毫无意义地导致整个功能无法使用。

Reads by default, writes only on request

默认仅读取，仅在请求时写入

The report is read-only. When the user asks for fixes, each change becomes an external write: invoke

/mutation-gate

and follow it. A refine pass typically proposes many small fixes at once, so state them as one set — issue key and exact command per row — rather than approving them one at a time.

报告为只读模式。当用户要求修复时，每项变更都需执行外部写入操作：调用

/mutation-gate

并遵循其流程。一次优化通常会同时提出许多小修复，因此应将它们整合为一组——每行包含问题键和精确命令——而非逐一审批。

Boundary with the neighbouring skills

与相邻技能的边界

Opening new work is
```
/rhdh-jira-create
```
.
Updating one known key — status, comment, assignee, link — is
```
/rhdh-jira-update
```
. Refinement reports across many issues; it does not replace that.
Building the next sprint from the refined backlog is
```
/rhdh-jira-sprint-plan
```
.
Exit criteria tables, field IDs, JQL, and the component catalog are
```
/rhdh-jira-api
```
.
Sizing scales, duplicate detection, and decomposition rules are
```
/rhdh-jira-authoring
```
.
What is still open against a release is
```
/rhdh-release-status
```
.

创建新工作项使用
```
/rhdh-jira-create
```
。
更新单个已知键（状态、评论、经办人、链接）使用
```
/rhdh-jira-update
```
。优化操作针对多个问题生成报告，不会替代该技能。
从已优化的待办事项构建下一个迭代使用
```
/rhdh-jira-sprint-plan
```
。
退出标准表、字段ID、JQL和组件目录属于
```
/rhdh-jira-api
```
的范畴。
规模评估标准、重复检测和分解规则属于
```
/rhdh-jira-authoring
```
的范畴。
查询版本中仍未完成的工作项使用
```
/rhdh-release-status
```
。

Completion

完成标准

Complete when every issue the report covers was actually fetched with its custom fields enriched — an unenriched search returns empty Story Points, Team, Size, and Sprint, which looks identical to a field nobody set and is the single most common source of a false "missing data" finding. Report the JQL, the issue count, and whether the result was truncated. Every finding names the check that produced it and its severity. A field that could not be retrieved is reported as unretrieved, never as missing.

当报告涵盖的每个问题都已获取并补充其自定义字段时，操作完成——未补充的搜索会返回空的Story Points、Team、Size和Sprint，这与未设置字段的情况看起来完全相同，是导致“数据缺失”误判的最常见原因。需报告JQL、问题数量以及结果是否被截断。每个发现需注明生成它的检查项及其严重程度。无法获取的字段应报告为“未获取”，而非“缺失”。