Back to Details

triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Triage

问题分流

Move issues on the project backlog through a small state machine of triage roles.
Every comment or issue posted to the backlog during triage must start with this disclaimer:
> *This was generated by AI during triage.*
通过一套由分流角色构成的小型状态机来推进项目待办事项中的问题流转。
在分流过程中发布到待办事项的每条评论或问题必须以以下免责声明开头：
> *This was generated by AI during triage.*

Reference docs

参考文档

  • AGENT-BRIEF.md — how to write durable agent briefs
  • OUT-OF-SCOPE.md — how the 
    .out-of-scope/
    knowledge base works
  • AGENT-BRIEF.md — 如何编写实用的Agent任务简报
  • OUT-OF-SCOPE.md — 
    .out-of-scope/
    知识库的运作方式

Roles

角色

Two category roles:
  • bug
    — something is broken
  • enhancement
    — new feature or improvement
Five state roles:
  • needs-triage
    — maintainer needs to evaluate
  • needs-info
    — waiting on reporter for more information
  • ready-for-agent
    — fully specified, ready for an AFK agent
  • ready-for-human
    — needs human implementation
  • wontfix
    — will not be actioned
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names — the actual label strings used on the backlog may differ. The mapping should have been provided to you - run 
/setup-matt-pocock-skills
if not.
State transitions: an unlabeled issue normally goes to 
needs-triage
first; from there it moves to 
needs-info
, 
ready-for-agent
, 
ready-for-human
, or 
wontfix
. 
needs-info
returns to 
needs-triage
once the reporter replies. The maintainer can override at any time — flag transitions that look unusual and ask before proceeding.
两种分类角色：
  • bug
    — 功能异常/缺陷
  • enhancement
    — 新功能或优化
五种状态角色：
  • needs-triage
    — 需由维护者评估
  • needs-info
    — 等待提交者补充信息
  • ready-for-agent
    — 已明确需求，可交由AFK Agent处理
  • ready-for-human
    — 需由人工实现
  • wontfix
    — 不予处理
每个完成分流的问题都应恰好带有一个分类角色和一个状态角色。若状态角色存在冲突，请先标记并咨询维护者后再进行后续操作。
这些是标准角色名称——待办事项中实际使用的标签文本可能有所不同。相关映射关系应已提供给你，若未提供，请执行
/setup-matt-pocock-skills
。
状态流转规则：未标记的问题通常首先进入
needs-triage
状态；从该状态可流转至
needs-info
、
ready-for-agent
、
ready-for-human
或
wontfix
状态。当提交者回复后，
needs-info
状态将转回
needs-triage
状态。维护者可随时覆盖上述规则——若遇到异常的状态流转，请先标记并咨询维护者后再继续。

Invocation

调用方式

The maintainer invokes 
/triage
and describes what they want in natural language. Interpret the request and act. Examples:
  • "Show me anything that needs my attention"
  • "Let's look at #42"
  • "Move #42 to ready-for-agent"
  • "What's ready for agents to pick up?"
维护者通过调用
/triage
并以自然语言描述需求。请解读请求并执行操作。示例：
  • "显示所有需要我关注的内容"
  • "查看#42号问题"
  • "将#42号问题移至ready-for-agent状态"
  • "哪些任务已准备好交由Agent处理？"

Show what needs attention

展示需关注的内容

Query the backlog and present three buckets, oldest first:
  1. Unlabeled — never triaged.
  2. needs-triage
     — evaluation in progress.
  3. needs-info
    with reporter activity since the last triage notes     — needs re-evaluation.
Show counts and a one-line summary per issue. Let the maintainer pick.
查询待办事项并按以下三个类别展示，按创建时间从早到晚排序：
  1. 未标记 — 从未进行过分流处理。
  2. needs-triage
     — 评估中。
  3. needs-info
    且自上次分流记录后提交者有新操作     — 需重新评估。
展示每个类别的问题数量以及每个问题的单行摘要，由维护者选择处理对象。

Triage a specific issue

分流单个特定问题

  1. Gather context. Read the full issue (body, comments, labels, reporter, dates). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read 
    .out-of-scope/*.md
    and surface any prior rejection that resembles this issue.
  2. Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.
  3. Reproduce (bugs only). Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong 
    needs-info
    signal). A confirmed repro makes a much stronger agent brief.
  4. Grill (if needed). If the issue needs fleshing out, run a 
    /grill-with-docs
    session.
  5. Apply the outcome:
    • ready-for-agent
      — post an agent brief comment (AGENT-BRIEF.md).
    • ready-for-human
      — same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
    • needs-info
      — post triage notes (template below).
    • wontfix
      (bug) — polite explanation, then close.
    • wontfix
      (enhancement) — write to 
      .out-of-scope/
      , link to it from a comment, then close (OUT-OF-SCOPE.md).
    • needs-triage
      — apply the role. Optional comment if there's partial progress.
  1. 收集上下文信息。阅读问题的完整内容（正文、评论、标签、提交者、日期）。解析之前的分流记录，避免重复询问已解决的问题。利用项目领域术语表探索代码库，遵循该领域的ADR（架构决策记录）。阅读
    .out-of-scope/*.md
    文件，找出与当前问题类似的过往拒绝案例。
  2. 给出建议。向维护者说明你推荐的分类和状态，并附上理由，以及与该问题相关的代码库简要概述。等待进一步指示。
  3. 复现问题（仅针对bug）。在询问提交者之前，尝试复现问题：阅读提交者提供的步骤，追踪相关代码，运行测试或命令。报告结果——成功复现并提供代码路径、复现失败，或信息不足（这是
    needs-info
    状态的强烈信号）。确认复现的问题能让Agent任务简报更精准。
  4. 询问补充信息（如有需要）。若问题需要进一步明确细节，启动
    /grill-with-docs
    会话。
  5. 执行处理结果：
    • ready-for-agent
      — 发布Agent任务简报评论（参考AGENT-BRIEF.md）。
    • ready-for-human
      — 采用与Agent任务简报相同的结构，但需注明无法委托给Agent的原因（如需要主观判断、外部访问权限、设计决策、手动测试等）。
    • needs-info
      — 发布分流记录（模板如下）。
    • wontfix
      （bug）——给出礼貌的解释后关闭问题。
    • wontfix
      （enhancement）——写入
      .out-of-scope/
      目录，在评论中链接至该文件后关闭问题（参考OUT-OF-SCOPE.md）。
    • needs-triage
      — 应用该状态角色。若有部分进展，可选择性发布评论。

Quick state override

快速状态覆盖

If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to 
ready-for-agent
without a grilling session, ask whether they want to write an agent brief.
若维护者要求“将#42号问题移至ready-for-agent状态”，请直接执行状态变更。先确认你即将执行的操作（角色变更、发布评论、关闭问题），再进行操作。跳过询问补充信息步骤。若未经过询问补充信息步骤就将问题移至
ready-for-agent
状态，请询问维护者是否需要编写Agent任务简报。

Needs-info template

补充信息请求模板

markdown
undefined
markdown
undefined

Triage Notes

Triage Notes

What we've established so far:
  • point 1
  • point 2
What we still need from you (@reporter):
  • question 1
  • question 2

Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".
What we've established so far:
  • point 1
  • point 2
What we still need from you (@reporter):
  • question 1
  • question 2

将询问补充信息过程中已明确的所有内容记录在“目前已确认的信息”部分，避免工作成果丢失。提出的问题必须具体且可执行，不能是“请提供更多信息”这类模糊表述。

Resuming a previous session

恢复之前的会话

If prior triage notes exist on the issue, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.
若该问题已有过往分流记录，请先阅读这些记录，检查提交者是否已回复未解决的问题，并在继续处理前展示最新情况。不要重复询问已解决的问题。