personal-triage

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Personal Triage

个人任务梳理（Personal Triage）

The personal sibling of the dev

triage

skill. It grooms raw items on the Personal Linear board (team key

JEG

) from

Triage

into a clear, classified, prioritized

Ready for Pickup

state, so a deep-work session only ever starts work that is already understood. Dev machinery (agent briefs, bug repro, Ready-for-Agent) is deliberately absent. For actual software projects it hands off to the dev

/triage

flow and gets out of the way.

You (James) are the only reporter, so there is no needs-info-from-reporter loop: when an item is unclear, grill the user directly and capture the answers on the card.

Every comment this skill posts MUST start with:

> *This was generated by AI during personal triage.*

这是开发

triage

技能的个人版。它会将Personal Linear看板（团队密钥

JEG

）上处于

Triage

状态的原始任务梳理为清晰、分类明确、已排优先级的

Ready for Pickup

状态，确保深度工作环节仅处理已明确的任务。开发相关机制（agent简报、bug复现、Ready-for-Agent）在此刻意省略。对于实际软件项目，它会移交至开发

/triage

流程，不再介入。

你（James）是唯一的报告人，因此无需“向报告人索要信息”的循环：当任务内容不明确时，直接向用户询问，并将答案记录在任务卡片上。

此技能发布的每条评论必须以以下内容开头：

> *This was generated by AI during personal triage.*

Tracker

跟踪工具

The board is the Personal Linear team (key

JEG

), via the Linear MCP (

list_issues

get_issue

save_issue

save_comment

list_comments

, loaded via ToolSearch). This skill only ever acts on the Personal team. For dev work it hands off (see Apps below) and never edits the dev board itself.

看板为Personal Linear团队（密钥

JEG

），通过Linear MCP（

list_issues

get_issue

save_issue

save_comment

list_comments

，通过ToolSearch加载）访问。此技能仅对Personal团队生效。对于开发工作，它会移交（见下方“应用场景”），绝不会编辑开发看板本身。

Board vocabulary

看板术语

Status = pipeline stage (columns). Personal triage works the left end:

```
Triage
```
: raw, needs grooming. The input.
```
Ready for Pickup
```
: groomed and ready to start. The main output.
```
In Progress
```
/
```
In Review
```
/
```
Done
```
: you own these; triage does not move them.
```
Backlog
```
: someday/maybe, kept but not now.
```
Canceled
```
: dropped (with a one-line why).
```
Duplicate
```
: folded into another card.

Kind = what sort of thing it is (exactly one label):

engineering

Task

Learning

Research

Errand

Admin

notes

engineering

means dev work (software, skills, repos, tooling). It doubles as the routing signal to the dev side. Existing-project work hands off to the dev flow and is not groomed here; a new app idea is the exception — flesh it out in the card, then park it in

Backlog

(see Apply the outcome).

notes

means zettelkasten note work (processing, linking, atomizing); these are run with

/link-your-thoughts

Priority = native Urgent / High / Medium / Low, default Medium. Re-read for personal life (it will not map exactly, and that is fine): Urgent = a hard external deadline this week; High = a real consequence if it slips; Medium = the default; Low = nice-to-have. Set one by the time a card leaves

Triage

Topic tags (optional, layered on top of the kind). A card may also carry a domain/topic label that is not a kind, e.g.

investing

(investing-domain work: research, analysis tools, checklist/mental-model skills). Apply these in addition to the one kind label, never instead of it.

A groomed card carries exactly one kind label, optionally one or more topic tags, a priority, and lands in exactly one status.

状态 = 流水线阶段（列）。个人任务梳理仅处理左侧起始端：

```
Triage
```
：原始状态，需梳理。为输入项。
```
Ready for Pickup
```
：已梳理完成，可开始执行。为主要输出项。
```
In Progress
```
/
```
In Review
```
/
```
Done
```
：由你负责；任务梳理不会移动这些状态的任务。
```
Backlog
```
：未来可能处理的任务，暂存但不立即执行。
```
Canceled
```
：已放弃（需附上一行说明原因）。
```
Duplicate
```
：合并至另一张卡片。

类型 = 任务所属类别（仅一个标签）：

engineering

、

Task

、

Learning

、

Research

、

Errand

、

Admin

、

notes

。

engineering

指开发工作（软件、技能、代码库、工具），同时作为移交至开发端的信号。现有项目的工作会移交至开发流程，不在此梳理；新应用想法是例外——需在卡片中完善内容，然后移至

Backlog

（见“执行结果”）。

notes

指zettelkasten笔记工作（整理、链接、拆分），这类任务通过

/link-your-thoughts

处理。

优先级 = 原生的Urgent / High / Medium / Low，默认Medium。结合个人场景重新理解（无需完全匹配，没问题）：Urgent = 本周有硬性外部截止日期；High = 延误将产生实际后果；Medium = 默认优先级；Low = 锦上添花的任务。任务离开

Triage

状态前需设置优先级。

主题标签（可选，在类型标签之上添加）。卡片还可添加不属于类型的领域/主题标签，例如

investing

（投资领域工作：研究、分析工具、清单/思维模型技能）。这些标签需附加在类型标签之上，不能替代类型标签。

已梳理完成的卡片需包含且仅包含一个类型标签，可选择性添加一个或多个主题标签，设置优先级，并归至唯一状态。

Show what needs attention

展示需关注的任务

Query the Personal board and present, oldest first:

Untriaged: in
```
Triage
```
with no kind label.
```
Triage
```
cards with grooming already in progress (notes present).

Show a one-line summary per card and let the user pick which to work.

查询Personal看板，按时间从早到晚展示：

未梳理任务：处于
```
Triage
```
状态且无类型标签。
正在梳理的
```
Triage
```
卡片（已有备注）。

每张卡片展示一行摘要，让用户选择要处理的任务。

Triage one item

梳理单个任务

Gather context. Read the card (title, description, comments, prior notes). If it points at a repo or skill (e.g.
```
munger/models.md
```
, the VPS crons), pull quick context from there so you do not ask what you can already find.
Recommend. State your kind + priority + outcome with reasoning. Wait for direction.
Grill if vague. If it is a fuzzy one-liner, ask focused questions one at a time until you know what it is and what "done" looks like. Capture the answers into the card description as you go.
Apply the outcome:
- Ready for Pickup: write a short brief into the description (What this is / Done means / First action), set the kind label and priority, move to
```
Ready for Pickup
```
  .
- engineering, existing project (hand off): if the work belongs to a repo/board that already exists (e.g. Docket dev work), confirm it is represented there (
```
/triage
```
  on that board), link the dev board or issue from the personal card, then close the personal card with a comment pointing across. No permanent double-tracking. Close as
```
Done
```
  when the dev side is already complete (a sign-off card);
```
Canceled
```
  when it is purely a stray pointer with nothing to track.
- engineering, new app idea (flesh out, then park): there is no board for not-yet-started apps, and standing up an empty repo per idea is wasteful. So when an app idea has life, flesh it out in the card itself during triage — grill the user one question at a time and capture: what it is, the spark (why it is interesting, in their words), the core mechanic, an MVP direction, and open questions for the dev brainstorm. Then label
```
engineering
```
  , set a priority, and move it to
```
Backlog
```
  . It waits there, understood and preserved, until the user commits to building it; at that point the handoff is
```
/startup
```
  (stand up the repo + board, which kicks off the brainstorm/grill), then
```
/triage
```
  . Note this handoff path in the card so it is not lost.
- Someday/maybe: move to
```
Backlog
```
  .
- Drop: move to
```
Canceled
```
  with a one-line why.
- Needs your decision: leave in
```
Triage
```
  , post the open question as a comment.
- Duplicate: move to
```
Duplicate
```
  , link the original.

收集上下文。阅读卡片（标题、描述、评论、过往备注）。如果卡片指向代码库或技能（例如
```
munger/models.md
```
、VPS定时任务），从中提取快速上下文，避免询问已能找到的信息。
给出建议。说明你建议的类型+优先级+处理方案及理由。等待用户指示。
若模糊则追问。如果任务是模糊的单行描述，逐个提出针对性问题，直到明确任务内容及“完成”的定义。将答案逐一记录到卡片描述中。
执行结果：
- Ready for Pickup：在描述中写入简短简报（任务内容/完成标准/第一步行动），设置类型标签和优先级，移至
```
Ready for Pickup
```
  状态。
- engineering，现有项目（移交）：如果工作属于已存在的代码库/看板（例如Docket开发工作），确认该任务已在对应看板中体现（在该看板上执行
```
/triage
```
  ），在个人卡片中链接开发看板或任务，然后添加跨链接评论并关闭个人卡片。不允许长期重复跟踪。若开发端已完成（验收卡片），则标记为
```
Done
```
  ；若只是无跟踪价值的零散指向，则标记为
```
Canceled
```
  。
- engineering，新应用想法（完善后暂存）：尚未启动的应用没有对应的看板，为每个想法创建空代码库是浪费的。因此，当应用想法有价值时，需在梳理过程中在卡片内完善内容——逐个向用户提问并记录：应用是什么、灵感来源（用户眼中的有趣之处）、核心机制、MVP方向、开发头脑风暴的待解决问题。然后标记
```
engineering
```
  类型，设置优先级，移至
```
Backlog
```
  状态。它会在此暂存，内容明确且保存完好，直到用户决定开发；此时移交流程为
```
/startup
```
  （创建代码库+看板，启动头脑风暴/追问），然后执行
```
/triage
```
  。需在卡片中注明此移交路径，避免遗漏。
- 未来可能处理：移至
```
Backlog
```
  状态。
- 放弃：移至
```
Canceled
```
  状态，并附上一行说明原因。
- 需你决策：保留在
```
Triage
```
  状态，将待解决问题作为评论发布。
- 重复任务：移至
```
Duplicate
```
  状态，链接原始任务。

Quick override

快速覆盖操作

If the user says "move JEG-7 to Ready for Pickup" or "drop JEG-9", trust them: confirm the change (status, label, comment, close), then apply it. Skip grilling.

如果用户说“将JEG-7移至Ready for Pickup”或“放弃JEG-9”，请信任用户：确认变更（状态、标签、评论、关闭），然后执行。跳过追问环节。

Definition of groomed

已梳理完成的定义

A card is

Ready for Pickup

when it has: a kind label, a priority, a one-line definition of done, and a clear first action. That is the whole bar. A full spec is only for

engineering

items, which get one on the dev side via

/startup

/grill-with-docs

卡片处于

Ready for Pickup

状态时需满足：有类型标签、有优先级、一行完成定义、明确的第一步行动。这就是全部要求。完整规格仅适用于

engineering

任务，这类任务会在开发端通过

/startup

/grill-with-docs

生成。

Pairs with

配套技能

The dev
```
triage
```
/
```
engineer
```
/
```
reviewer
```
flow, which owns anything labelled
```
engineering
```
once it has been handed off.

开发
```
triage
```
/
```
engineer
```
/
```
reviewer
```
流程，一旦
```
engineering
```
任务移交后，由该流程负责处理。