Back to Details

ticket

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ticket — Artifact Creation

工单——工件创建

All skill output that needs to persist goes into a ticket. No custom directories.
所有需要持久化的Skill输出都要存入工单中，禁止使用自定义目录。

Tag Taxonomy

标签分类体系

Every artifact ticket MUST use the appropriate tags:
Artifact typeTagsExample title
Oracle research
research, oracle
"Oracle: Why API latency spiked"
Delphi investigation (epic)
research, delphi
"Delphi: Database migration strategy"
Delphi synthesis
research, delphi-synthesis
"Delphi synthesis: Database migration strategy"
Implementation plan
plan
"Plan: Refactor auth middleware"
Architecture decision
decision
"ADR: Use Zustand for state management"
Postmortem
postmortem
"Postmortem: Agent skipped codebase exploration"
Code review
review
"Review: PR #42 auth changes"
Design spec
design-spec
"Design spec: Dashboard redesign"
每个工件工单必须使用对应的标签：
工件类型标签示例标题
Oracle研究
research, oracle
"Oracle：API延迟突增原因"
Delphi调查（史诗工单）
research, delphi
"Delphi：数据库迁移策略"
Delphi综合分析
research, delphi-synthesis
"Delphi综合分析：数据库迁移策略"
实施计划
plan
"Plan：重构认证中间件"
架构决策
decision
"ADR：使用Zustand进行状态管理"
事后分析
postmortem
"Postmortem：Agent跳过代码库探索事件"
代码评审
review
"Review：PR #42 认证变更"
设计规范
design-spec
"Design spec：仪表盘重设计"

Creating Artifact Tickets

创建工件工单

Use 
tk
(via 
todos_oneshot
or 
todos
tool):
todos_oneshot(
  title: "Oracle: <topic>",
  description: "<full findings>",
  tags: "research,oracle",
  type: "task"
)
使用
tk
（通过
todos_oneshot
或
todos
工具）：
todos_oneshot(
  title: "Oracle: <topic>",
  description: "<full findings>",
  tags: "research,oracle",
  type: "task"
)

Epics with Subtasks

包含子任务的史诗工单

For multi-part artifacts (e.g. Delphi = N oracles + synthesis):
  1. Create the epic ticket first
  2. Create subtask tickets linked to it
  3. Use 
    teams delegate
    to run subtasks in parallel
  4. Update the epic with synthesized results
undefined
对于多部分工件（例如Delphi = N个Oracle研究 + 综合分析）：
  1. 首先创建史诗工单
  2. 创建关联到它的子任务工单
  3. 使用
    teams delegate
    并行运行子任务
  4. 将综合结果更新到史诗工单中
undefined

1. Epic

1. 史诗工单

todos_oneshot(title: "Delphi: <topic>", tags: "research,delphi", type: "epic")
todos_oneshot(title: "Delphi: <topic>", tags: "research,delphi", type: "epic")

2. Subtasks (one per oracle)

2. 子任务（每个Oracle对应一个）

todos_oneshot(title: "Oracle 1: <topic>", tags: "research,oracle", type: "task") todos_oneshot(title: "Oracle 2: <topic>", tags: "research,oracle", type: "task") todos_oneshot(title: "Oracle 3: <topic>", tags: "research,oracle", type: "task")
todos_oneshot(title: "Oracle 1: <topic>", tags: "research,oracle", type: "task") todos_oneshot(title: "Oracle 2: <topic>", tags: "research,oracle", type: "task") todos_oneshot(title: "Oracle 3: <topic>", tags: "research,oracle", type: "task")

3. teams delegate to run in parallel

3. 使用teams delegate并行运行

4. Synthesize into epic

4. 将结果综合到史诗工单

undefined
undefined

Rules

规则

  1. No custom output directories. No 
    .oracle/
    , 
    .plans/
    , 
    .design-specs/
    , 
    docs/postmortems/
    , 
    docs/research/
    .
  2. Tags are mandatory. Every artifact ticket uses tags from the taxonomy above.
  3. Titles are descriptive. Prefix with artifact type (Oracle:, Plan:, ADR:, etc.).
  4. Full content in the ticket. The ticket body IS the artifact — not a pointer to a file elsewhere.
  5. Link related tickets. Subtasks link to epics. Plans link to implementation tickets. Postmortems link to the incident tickets.
  1. 禁止使用自定义输出目录。不得创建.oracle/、.plans/、.design-specs/、docs/postmortems/、docs/research/等目录。
  2. 标签为必填项。每个工件工单必须使用上述分类体系中的标签。
  3. 标题需具有描述性。前缀需包含工件类型（Oracle:、Plan:、ADR:等）。
  4. 完整内容存入工单。工单正文即为工件本身——不得指向其他位置的文件。
  5. 关联相关工单。子工单需关联到史诗工单。计划需关联到实施工单。事后分析需关联到事件工单。