task-os

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Task OS

Taskwarrior (

task

) is the source of truth — not memory, not chat history, not assumptions. Ground every interaction in task state before acting.

Taskwarrior（

task

）是唯一可信来源——而非记忆、聊天记录或假设。在采取任何行动前，所有交互都必须基于任务状态。

Orient

状态确认

Before acting on any request, check current state:

bash

task next limit:10             # highest urgency
task +OVERDUE list             # past due
task +waiting list             # blocked on others

For software tasks, also check the repo:

bash

git -C <repo-path> status --short
git -C <repo-path> log --oneline -5

Skip git checks for non-code domains (stocks, life, errands).

After orienting, fix state hygiene:

Every active project should have at least one
```
+next
```
task.
Re-evaluate stale
```
+waiting
```
tasks.
Close work that's already done but not yet marked.

在处理任何请求前，先检查当前状态：

bash

task next limit:10             # highest urgency
task +OVERDUE list             # past due
task +waiting list             # blocked on others

对于软件类任务，还需检查代码仓库：

bash

git -C <repo-path> status --short
git -C <repo-path> log --oneline -5

非代码领域（如股票、生活、跑腿事务）无需执行git检查。

完成状态确认后，优化状态整洁度：

每个活跃项目至少包含一个
```
+next
```
任务。
重新评估长期处于
```
+waiting
```
状态的任务。
标记所有已完成但未归档的任务为完成。

Periodic check-in

周期性检查

When waking on a timer or heartbeat with no user message:

Orient (as above).
Check for stalls — any active task with no recent progress?
If something is stalled, attempt recovery.
If there's a clear
```
+next
```
task with no blockers, pick it up.
If nothing needs attention, go idle. Don't manufacture work.

当定时触发或无用户消息的心跳机制启动时：

执行状态确认（如上所述）。
检查停滞任务——是否有活跃任务未取得任何进展？
若存在停滞任务，尝试恢复。
若存在明确且无阻塞的
```
+next
```
任务，立即执行。
若无需要处理的事项，进入空闲状态，不得凭空制造工作。

Morning briefing

晨间简报

When the user starts their day ("morning", "briefing", "what's on today"):

bash

task +OVERDUE list
task +TODAY list
task +next list
task +WEEK list
task summary

Deliver a concise rundown:

Overdue (needs attention now)
Due today
Top next actions across projects
Anything waiting that may have unblocked

Keep it scannable — short lines, no wide tables. This lands on a phone screen.

当用户开启新一天（输入“morning”、“briefing”、“what's on today”）：

bash

task +OVERDUE list
task +TODAY list
task +next list
task +WEEK list
task summary

提供简洁概览：

逾期任务（需立即处理）
今日到期任务
跨项目的核心后续行动
可能已解除阻塞的等待任务

内容需便于快速浏览：短句呈现，避免宽表格，适配手机屏幕。

Quick capture

快速捕获

Any "remind me", "I need to", "add a task", or loose intent → straight to inbox:

bash

task add project:inbox "The thing they said"

Assign project/tags/priority only if the user provides enough context. Otherwise capture fast, organize later.

任何包含“remind me”、“I need to”、“add a task”的模糊需求，直接存入收件箱：

bash

task add project:inbox "The thing they said"

仅当用户提供足够上下文时，才为任务分配项目、标签或优先级。否则先快速捕获，后续再整理。

Execution

执行流程

Evidence over claims

以结果为依据

Progress means different things per domain:

Code: a commit, a file written, a test result.
Stocks/research: an annotation, an analysis note, a saved artifact.
Life/errands: marking the task done is sufficient.

Never say "I worked on X" without pointing to the result.

不同领域的“进展”定义不同：

代码领域：提交记录、已编写文件、测试结果。
股票/研究领域：标注内容、分析笔记、已保存的研究成果。
生活/跑腿事务：标记任务为完成即可。

不得仅说“我在处理X”，必须同步展示结果。

One thing at a time

一次只做一件事

Break work into steps. Finish and record each before moving to the next.

将工作拆分为步骤。完成并记录当前步骤后，再进行下一步。

Task lifecycle

任务生命周期

task add project:X "Do the thing" +next
task <id> start
task <id> annotate "what happened, what's left"
task <id> done
task add project:X "Next step" +next

When blocked:

task <id> modify +blocked
task add project:X "Unblock: <reason>" +next

When waiting on someone/something:

task <id> modify +waiting
task <id> annotate "Waiting on: <who/what>"

task add project:X "Do the thing" +next
task <id> start
task <id> annotate "what happened, what's left"
task <id> done
task add project:X "Next step" +next

当任务阻塞时：

task <id> modify +blocked
task add project:X "Unblock: <reason>" +next

当任务需等待他人/其他事项时：

task <id> modify +waiting
task <id> annotate "Waiting on: <who/what>"

Stall detection

停滞检测

Flag work as stalled when:

An active task has no progress and no annotation since it was started.
A previous attempt failed with no retry or blocker task created.
A plan was made but no execution task exists.
The user asked for something and no task captures it.

出现以下情况时，标记任务为停滞：

活跃任务启动后无进展且无任何注释。
之前的尝试失败，但未创建重试任务或阻塞任务。
已制定计划，但未创建执行任务。
用户提出需求，但未创建对应任务。

Recovery

停滞恢复

Root-cause in one sentence.
Record it:
```
task <id> annotate "Stalled: <cause>"
```
.
Create a path forward:
- Blocker task if external (
```
+blocked
```
  or
```
+waiting
```
  )
- Retry task with narrower scope (
```
+next
```
  )
Execute the smallest viable next step.
Report the state change.

用一句话说明根本原因。
记录原因：
```
task <id> annotate "Stalled: <cause>"
```
。
制定解决方案：
- 若为外部阻塞，创建阻塞任务（标记
```
+blocked
```
  或
```
+waiting
```
  ）
- 若为范围过大，创建更细分的重试任务（标记
```
+next
```
  ）
执行最小可行的下一步操作。
同步状态变更。

State hygiene

状态整洁度维护

After completing work or ending a conversation:

Every piece of in-progress work has a task.
Tasks have enough annotations for someone with zero prior context.
Every active project has a
```
+next
```
task.
Blockers and open questions are captured.

This is not optional. Future conversations depend on clean state.

完成工作或结束对话后：

所有进行中的工作均有对应任务。
任务包含足够注释，确保无前置背景的人也能理解。
每个活跃项目至少包含一个
```
+next
```
任务。
所有阻塞项和未解决问题均已记录。

此要求为强制性，后续对话依赖于整洁的状态。

Weekly review

每周回顾

When the user says "review" or "weekly review":

Process inbox to zero — assign project, tags, priority, or delete.
Review
```
+waiting
```
— anything unblocked? Poke anyone?
Review
```
+OVERDUE
```
— reschedule or escalate.
Check each project has a
```
+next
```
task:
```
task summary
```
.
Review
```
+someday
```
— promote or drop.
Show completed this week:
```
task end.after:today-7d completed
```
.
Show burndown:
```
task burndown.weekly
```
.

当用户输入“review”或“weekly review”时：

清空收件箱——为任务分配项目、标签、优先级，或删除无用任务。
回顾
```
+waiting
```
任务——是否有已解除阻塞的任务？是否需要跟进相关人员？
回顾
```
+OVERDUE
```
任务——重新安排时间或升级优先级。
通过
```
task summary
```
检查每个活跃项目是否包含
```
+next
```
任务。
回顾
```
+someday
```
任务——提升优先级或删除。
展示本周完成的任务：
```
task end.after:today-7d completed
```
。
展示燃尽图：
```
task burndown.weekly
```
。

Status report

状态报告

When the user asks "status":

Active — what's in flight Done — what completed (with evidence) Blocked — what's stuck and why Next — what comes after

Short. Concrete. No filler.

当用户询问“status”时：

进行中——当前正在处理的任务 已完成——已完成的任务（附结果） 阻塞中——停滞的任务及原因 下一步——后续计划

内容简洁、具体，无冗余信息。

Conventions

约定规范

Project hierarchy

项目层级

work.{org}.{repo}            # software projects
stocks.{TICKER}              # per-ticker analysis
stocks.macro                 # market-level
life.{area}                  # health, finances, errands, travel
personal.{area}              # personal projects
inbox                        # unprocessed capture

Run

task projects

first. Follow existing structure before creating new ones.

work.{org}.{repo}            # 软件项目
stocks.{TICKER}              # 单只股票分析
stocks.macro                 # 宏观市场分析
life.{area}                  # 健康、财务、跑腿、旅行
personal.{area}              # 个人项目
inbox                        # 未处理的捕获任务

先执行

task projects

查看现有结构，遵循已有结构后再创建新项目。

Dynamic grouping

动态分组

Start narrow — one task or sub-project per distinct concern:

stocks.AAPL                        # single ticker
inbox.jodie_lamp                   # one conversation thread
work.acme.backend_auth             # one work stream

When multiple tasks share context, consolidate under a topic:

inbox.nordic_lamps_feb2026         # absorbs jodie_lamp + marcus_lamp + ikea_order
stocks.ai_chip_plays               # groups NVDA + AMD analysis
work.acme.q1_launch                # groups backend_auth + frontend_onboarding

Name grouped projects by topic, not by source, once it's multi-party.
Move existing tasks into the new parent rather than duplicating.
This applies everywhere: inbox threads, stock themes, work initiatives, research topics.

初始时按单一关注点创建任务或子项目：

stocks.AAPL                        # 单只股票AAPL
inbox.jodie_lamp                   # 单条对话线程jodie_lamp
work.acme.backend_auth             # 单个工作流backend_auth

当多个任务共享上下文时，按主题合并为父项目：

inbox.nordic_lamps_feb2026         # 合并jodie_lamp + marcus_lamp + ikea_order
stocks.ai_chip_plays               # 合并NVDA + AMD分析
work.acme.q1_launch                # 合并backend_auth + frontend_onboarding

多来源的分组项目需按主题命名，而非来源。
将现有任务移入新的父项目，不得重复创建。
此规则适用于所有领域：收件箱线程、股票主题、工作举措、研究课题。

Priorities

优先级

```
H
```
— blocking others or time-sensitive
```
M
```
— important, not urgent
```
L
```
— nice to have
None — backlog

```
H
```
——阻塞他人或时间敏感
```
M
```
——重要但不紧急
```
L
```
——锦上添花
无标记——待办清单

Communication

沟通规范

Short, stateful updates. What changed, what's next.
Don't announce intent — do the thing, then report.
Surface blockers proactively.
Format for a phone screen: short lines, no wide tables, scannable.

简短、基于状态的更新：说明已变更内容及下一步计划。
不要宣布意图——先执行，再同步结果。
主动暴露阻塞项。
适配手机屏幕：短句呈现，避免宽表格，便于快速浏览。

task-os

Original

Translation

Task OS

Task OS

Orient

状态确认

Periodic check-in

周期性检查

Morning briefing

晨间简报

Quick capture

快速捕获

Execution

执行流程

Evidence over claims

以结果为依据

One thing at a time

一次只做一件事

Task lifecycle

任务生命周期

Stall detection

停滞检测

Recovery

停滞恢复

State hygiene

状态整洁度维护

Weekly review

每周回顾

Status report

状态报告

Conventions

约定规范

Project hierarchy

项目层级

Dynamic grouping

动态分组

Tags

标签

Priorities

优先级

Communication

沟通规范