$ loading_
用标签驱动的问题分诊流程，规范状态流转并生成可追溯分诊记录。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "triage-workflow" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/triage-workflow/SKILL.md 2. 保存为 ~/.claude/skills/triage-workflow/SKILL.md 3. 装好后重载技能，告诉我可以用了
请使用 triage-workflow 对这个 GitHub Issue 进行分诊：检查现有标签，判断当前状态，按规则推进到下一状态，并生成可保存的分诊记录与后续建议。
输出更新后的分诊状态、应调整的标签、分诊结论，以及可继续恢复的分诊记录。
基于之前保存的分诊记录，继续处理这个工作项：恢复上次状态，核对当前标签是否一致，如有新信息则重新评估并推进到正确状态。
输出恢复后的上下文、最新状态判断、标签修正建议，以及续办后的分诊结果。
请对这个 Azure DevOps 工作项执行 triage-workflow：根据标签和内容判断其分诊阶段，完成合法状态迁移，并生成可审计的分诊产物。
得到明确的阶段归类、状态迁移说明、需要补充的信息，以及标准化分诊记录。
| State | Description |
|---|---|
unlabeled | New issue, never triaged |
needs-triage | Maintainer needs to evaluate |
needs-info | Waiting on reporter for more information |
ready-for-agent | Fully specified, ready for autonomous agent implementation |
ready-for-human | Requires human implementation |
wontfix | Will not be actioned |
Every issue should have exactly one state label. If conflicting state labels exist, flag the conflict and ask the maintainer which is correct.
| From | To | Who triggers | What happens |
|---|---|---|---|
unlabeled | needs-triage | Skill (first look) | Issue needs evaluation; apply label |
unlabeled | ready-for-agent | Maintainer | Well-specified, agent-suitable; write agent brief, apply label |
unlabeled | ready-for-human | Maintainer | Requires human; write summary, apply label |
unlabeled | wontfix | Maintainer | Out of scope or duplicate; close with comment |
needs-triage | needs-info | Maintainer | Underspecified; post triage notes with questions |
needs-triage | ready-for-agent | Maintainer | Clarification complete, agent-suitable; write agent brief |
needs-triage | ready-for-human | Maintainer | Clarification complete, needs human; write summary |
needs-triage | wontfix | Maintainer | Decided not to action; close with comment |
needs-info | needs-triage | Skill (detects reply) | Reporter replied; resurface for re-evaluation |
Only these transitions are valid. Flag unusual transitions.
Triage notes, agent briefs, summaries, comments, and any label-driven artifacts written to the board follow the Content Style rules in the work-item-creation skill: no emojis or decorative Unicode, no em-dash or hyphen as separator between concepts, never #<number> in free text (Azure DevOps auto-links it), no contrastive framing, direct active voice, no promotional language, short concrete prose.
When this skill writes any content to GitHub or Azure DevOps (state-change comments, agent briefs, info requests), apply those rules before sending.
State is managed via labels:
| Label | Color (hex) |
|---|---|
needs-triage | fbca04 |
needs-info | d93f0b |
ready-for-agent | 0e8a16 |
ready-for-human | 1d76db |
wontfix | e4e669 |
When transitioning: remove old state label, add new state label. Ensure the category label (bug or enhancement) is also present.
Map states to the process template's workflow states (per board-config). Use tags for supplementary classification (ready-for-agent, needs-info).
ready-for-agent)Post as a comment on the issue:
> This was generated by AI during triage.
## Agent Brief
**Objective**: [What needs to be built or fixed, in domain language]
**Acceptance criteria**:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
**Context**: [What the agent needs to know about the codebase area]
**Constraints**: [Any limits on the approach]
Durability rules apply: no file paths, no line numbers. Describe behavior and domain concepts.
needs-info)Post as a comment:
> This was generated by AI during triage.
## Triage Notes
**What we have established so far:**
- [Point 1]
- [Point 2]
**What we still need from you (@reporter):**
- [Specific, actionable question 1]
- [Specific, actionable question 2]
Include everything resolved during the clarification session. Questions must be specific, not vague ("please provide more info").
ready-for-human)Post as a comment with the same structure as agent brief, plus:
**Why this needs human implementation**: [Reason: judgment calls, external system access, design decisions, manual testing]
…
沉淀并查询代码库经验教训，帮助开发、验证与评审减少重复踩坑。
在开发任务完成后，智能推荐最合适的下一步实施工作。
系统化排查测试失败、构建中断与异常运行问题，帮助快速恢复开发进度
为软件架构图提供设计与审查建议，提升文档中的图示清晰度与规范性
帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。
提取并维护领域术语表，统一规范术语、识别歧义并校验文档一致性。
在开始处理 GitHub 或 Azure 工作项前，核对负责人、依赖、优先级与产能。
帮助团队用历史数据相似检索与组件分类来分流 GitHub 问题。
帮助你规范创建 GitHub Issues 或 Azure DevOps 的任务、需求与史诗条目。
帮助团队快速分诊客服工单，判定优先级、归属团队与是否重复问题。
分析 GitHub 与 Discord 信号，帮助维护者判断项目优先级与待处理事项。
帮助团队统筹 GitHub 与 Linear 的任务流、PR 分诊和执行协同。