rhdh-jira-authoring

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

RHDH Jira authoring

RHDH Jira工作项撰写

The material that decides whether an issue is worth reading six months later. Two skills use it —

/rhdh-jira-create

while drafting and

/rhdh-jira-refine

while auditing — so it lives here rather than in either of them.

This skill produces text and judgements. It never runs a Jira command and never performs a write.

这些内容决定了一个工作项在六个月后是否仍有阅读价值。有两个技能会用到它——起草时使用

/rhdh-jira-create

，评审时使用

/rhdh-jira-refine

——因此它独立存在于这两个技能之外。

本技能仅生成文本和判断结果，从不执行任何Jira命令，也不会进行写入操作。

Route by need

按需选择指引

Need	Load
How to challenge a draft; how to infer RHDH Jira fields from conversation	references/grill.md
T-shirt sizes, story points, RHDHSUPP effort points, sizing challenges	references/sizing.md
Does this already exist?	references/duplicates.md
Splitting a Feature into Epics or an Epic into Stories	references/work-breakdown.md

需求	参考文档
如何评审草稿；如何从对话中推导RHDH Jira字段	references/grill.md
T-shirt规模、故事点、RHDHSUPP工作量点、规模评审方法	references/sizing.md
是否已有重复工作项？	references/duplicates.md
将Feature拆分为Epics或Epic拆分为Stories	references/work-breakdown.md

Templates and examples

模板与示例

Description templates are Jira wiki markup. Each has a filled example next to it for tone and detail calibration — read the example before drafting, because the templates alone underspecify how much detail an RHDH reviewer expects.

Issue type	Usual project	Template	Example
Feature	RHDHPLAN	`assets/templates/feature.txt`	`assets/examples/feature-example.txt`
Epic	RHIDP	`assets/templates/epic.txt`	`assets/examples/epic-example.txt`
Story	RHIDP	`assets/templates/story.txt`	`assets/examples/story-example.txt`
Task	RHIDP	`assets/templates/task.txt`	`assets/examples/task-example.txt`
Bug	RHDHBUGS	`assets/templates/bug.txt`	`assets/examples/bug-example.txt`

Spikes use the Task template with a

SPIKE:

prefix on the summary and a time-boxed story point estimate. A Vulnerability uses the Story template and always carries the Security component. Feature Request and Outcome templates exist in RHDHPLAN; this skill does not carry them, so draft those from the project's own template in the Jira UI.

Sub-tasks are children of an existing issue, never standalone.

A filled template is wiki markup, and Jira Cloud will render it as literal

h1.

and

*text*

unless it is converted to ADF first.

/rhdh-jira-api

owns that conversion.

描述模板采用Jira wiki标记语言。每个模板旁都配有已填充的示例，用于校准语气和细节程度——起草前请先阅读示例，因为仅靠模板无法明确RHDH评审人员期望的详细程度。

工作项类型	常用项目	模板	示例
Feature	RHDHPLAN	`assets/templates/feature.txt`	`assets/examples/feature-example.txt`
Epic	RHIDP	`assets/templates/epic.txt`	`assets/examples/epic-example.txt`
Story	RHIDP	`assets/templates/story.txt`	`assets/examples/story-example.txt`
Task	RHIDP	`assets/templates/task.txt`	`assets/examples/task-example.txt`
Bug	RHDHBUGS	`assets/templates/bug.txt`	`assets/examples/bug-example.txt`

Spike使用Task模板，只需在摘要前添加

SPIKE:

前缀，并给出时间盒式的故事点估算。漏洞问题使用Story模板，且必须关联Security组件。RHDHPLAN中存在Feature Request和Outcome模板，但本技能未包含这些模板，需通过Jira UI使用项目自身的模板进行起草。

子任务必须依附于现有工作项，不能独立存在。

已填充的模板采用wiki标记语言，Jira Cloud会将

h1.

和

*text*

等标记视为文本内容，除非先将其转换为ADF格式。

/rhdh-jira-api

负责完成该转换工作。

Boundary with the neighbouring skills

与相邻技能的边界

Running the interview and creating the issue is
```
/rhdh-jira-create
```
.
Auditing issues that already exist is
```
/rhdh-jira-refine
```
.
Field IDs, the component catalog, JQL,
```
acli
```
syntax, and workflow exit criteria are
```
/rhdh-jira-api
```
.
The general interview cadence is the external
```
grilling
```
skill, invoked by name. What is here is only the RHDH-specific half.

开展访谈并创建工作项由
```
/rhdh-jira-create
```
负责。
评审已存在的工作项由
```
/rhdh-jira-refine
```
负责。
字段ID、组件目录、JQL、
```
acli
```
语法和工作流退出标准由
```
/rhdh-jira-api
```
负责。
通用访谈节奏由外部
```
grilling
```
技能负责，需通过名称调用。本技能仅包含RHDH专属的部分内容。

Completion

完成标准

Complete when the draft names its template and its issue type, every section the template asks for is either filled or explicitly marked out of scope, every applicable challenge in the matrix has been applied or skipped with a stated reason, and the proposed size cites the scale it came from rather than a feeling. A duplicate check reports the query it ran and the row count it saw. Nothing here is complete on the strength of a draft the user has not seen.

当草稿明确标注了所使用的模板和工作项类型、模板要求的每个部分均已填充或明确标记为超出范围、挑战矩阵中所有适用的评审项均已应用或给出跳过理由、提议的规模明确说明所采用的估算尺度而非仅凭感觉时，即视为完成。重复项检查需报告执行的查询语句和查询到的行数。未经过用户确认的草稿不能视为完成。