new-work

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

New Work

新工作

Todo notes track work items as markdown files with YAML front matter capturing status, context, and progress.

待办事项笔记将工作项记录为带有YAML前置元数据的Markdown文件，用于捕获状态、上下文和进度。

Storage Location

存储位置

Use

_dev/todos/

if it exists in the repository root; otherwise ask the user where to store todo notes before creating anything. It contains two subdirectories:

pending/

(active) and

done/

(finished).

如果仓库根目录下存在

_dev/todos/

，则使用该目录；否则在创建任何内容前询问用户待办事项笔记的存储位置。该目录包含两个子目录：

pending/

（进行中）和

done/

（已完成）。

File Naming

文件命名

YYYY-MM-DD_short-kebab-slug.md

, e.g.

2026-02-18_add-oauth-support.md

YYYY-MM-DD_short-kebab-slug.md

，例如

2026-02-18_add-oauth-support.md

。

File Contents

文件内容

YAML front matter plus a markdown body. Only

status

is required.

markdown

---
status: pending   # pending | in progress | review | blocked | done
issue: https://github.com/org/repo/issues/123   # optional
pr: https://github.com/org/repo/pull/456        # optional
---

YAML前置元数据加上Markdown正文。仅

status

为必填项。

markdown

---
status: pending   # pending | in progress | review | blocked | done
issue: https://github.com/org/repo/issues/123   # optional
pr: https://github.com/org/repo/pull/456        # optional
---

Title

标题

Overview of what this is about and why it matters.

关于此项工作的概述及其重要性。

Key Files

关键文件

```
src/relevant-file.ts
```
— what it does
```
src/other-file.ts:functionName()
```
— why it matters

```
src/relevant-file.ts
```
— 功能说明
```
src/other-file.ts:functionName()
```
— 重要性说明

Work Items

工作项

First thing to do
Second thing to do

待完成的第一件事
待完成的第二件事

Design Decisions

设计决策

Context, constraints, or choices worth capturing.

值得记录的上下文、约束条件或选择。

Decision Log

决策日志

<!--

YYYY-MM-DD — Short Decision Title

YYYY-MM-DD — 简短决策标题

Decision: What was decided? Rationale: Why? -->

undefined

决策: 做出了什么决定？ 理由: 为什么这样决定？ -->

undefined

Lifecycle

生命周期

Create: make
```
pending/
```
if needed, create the date-prefixed file with
```
status: pending
```
, and write enough context to resume later.
In progress: update
```
status
```
; add
```
issue
```
/
```
pr
```
links when they exist; check off Work Items (
```
- [ ]
```
→
```
- [x]
```
); record significant decisions in the Decision Log.
Complete: set
```
status: done
```
and
```
mv
```
the file from
```
pending/
```
to
```
done/
```
.

创建: 若需要则创建
```
pending/
```
目录，创建带日期前缀的文件并设置
```
status: pending
```
，写入足够的上下文以便后续继续工作。
进行中: 更新
```
status
```
；当存在相关issue或PR时添加链接；勾选已完成的工作项（
```
- [ ]
```
→
```
- [x]
```
）；在决策日志中记录重要决策。
完成: 设置
```
status: done
```
并使用
```
mv
```
命令将文件从
```
pending/
```
移动到
```
done/
```
。

Keeping the Document Current

保持文档更新

Treat the todo as a living record for the rest of the session. Update it after any decision, newly discovered problem or requirement, issue raised/resolved, significant implementation work, or commit. When in doubt, update it.

When you form a plan — whether in response to a user request or on your own initiative — write it to the todo document rather than presenting it only in chat. The document is the persistent record; the chat is not.

To resume in a future session, use

/working-on <path-to-todo>

— same live-document behavior without re-creating the file.

在整个工作会话中，将待办事项文档视为动态记录。在做出任何决策、发现新问题或需求、问题提出/解决、完成重要实现工作或提交代码后，都要更新文档。如有疑问，就更新它。

当你制定计划时——无论是响应用户请求还是主动规划——都要将计划写入待办事项文档，而不是仅在聊天中呈现。文档是持久记录，聊天不是。

若要在未来会话中继续工作，使用

/working-on <path-to-todo>

命令——无需重新创建文件即可获得相同的动态文档功能。