work-brief

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Explain the work produced in this session so the operator can regain context and decide what to do next.

说明本次会话完成的工作，以便操作者恢复上下文并决定下一步行动。

Default: summarize the current local diff; if no local diff exists, summarize the current branch versus the resolved base branch.
If the operator passes a commit, branch, PR text, ticket id, or topic, use that as the target when possible.
This is for the human operator, not another agent. Use
```
handoff
```
for a resumable agent-to-agent transfer.

Inspect
```
git status --short
```
, current branch, recent commits, staged diff, unstaged diff, and untracked files.
If no local diff exists, resolve the base branch via
```
.turkit.yaml → base_branch
```
, remote HEAD, then
```
main
```
; compare base to current branch.
Read
```
references/output-preferences.md
```
and apply the configured output language/style.
Read only the files needed to explain the main behavior, important decisions, verification evidence, and current state.
Group the work into 2-4 meaningful pieces. Prefer product/domain boundaries over file types.
Link only the key files. Do not list every changed file.

Respond using the configured output language. Aim for one screen, roughly 25-45 lines. Use this shape:

markdown

<ticket or subject> fait. Voilà l'essentiel :

使用配置的输出语言进行响应。目标为一屏内容，约25-45行。采用以下格式：

markdown

<ticket or subject> fait. Voilà l'essentiel :

<3-5 lines: what was built/changed, not a file list>

<2-4 lines: pain solved, goal, or tradeoff. If not visible, say so.>


For English conversations, translate the headings naturally (`What`, `Why`, `Pieces`, `Quality`, `State`).


对于英文对话，需将标题自然翻译为英文（`What`, `Why`, `Pieces`, `Quality`, `State`）。

Read-only: do not stage, commit, push, edit, create branches, update tickets, or create PRs.
Do not output a long audit, full code tour, or file-by-file walkthrough.
Do not claim tests/checks/reviews passed unless there is explicit evidence from the current session, logs, or repo state.
Do not invent why a change was made. If intent is not visible, say "not obvious from the diff".
Keep links to 3-8 important files max. If a file line matters and is known, link the line.
If the work is too large for one screen, summarize the top pieces and end with
```
Open next: <file or command>
```
.

Apply

references/output-preferences.md

for operator-facing language/style.

应用

references/output-preferences.md

中面向操作者的语言/风格要求。