tracking-tasks

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

tracking-tasks — Task Persistence & Lifecycle Synchronization

tracking-tasks — 任务持久化与生命周期同步

Operating Invariants

运行约束

Storage Exclusivity: Mutate task records exclusively in the configured tracker from
```
.agents/task-tracker.md
```
(Local Markdown
```
.agents/tasks/
```
, GitHub Issues, GitLab, or Linear); never touch production code.
State Integrity: Maintain canonical states:
```
ready
```
,
```
in-progress
```
,
```
done
```
. Treat
```
blocked
```
as a derived state based on prerequisite tasks; a task is only
```
ready
```
when all predecessor dependencies are
```
done
```
.
Idempotent Synchronization: Check existing issues/files before creating; re-read after writing to verify IDs and persistence.
Self-Contained Payloads: Embed acceptance criteria, verification commands, and parent traces into the stored task body so subagents can execute independently.
Adaptive Invocation Output: Render a persistence summary table for humans; emit a compact micro-token for autonomous runners.

存储独占性：仅在已配置的 Issue Tracker 中修改任务记录；存储位置由
```
.agents/task-tracker.md
```
指定（Local Markdown
```
.agents/tasks/
```
、GitHub Issues、GitLab 或 Linear）；绝不触碰生产代码。
状态完整性：维护规范状态：
```
ready
```
、
```
in-progress
```
、
```
done
```
。将
```
blocked
```
视为基于前置任务派生的状态；仅当所有前置依赖均为
```
done
```
时，任务才是
```
ready
```
。
幂等同步：创建前检查现有 Issue 或文件；写入后重新读取，以验证 ID 和持久化结果。
自包含载荷：将验收标准、验证命令和父级溯源信息嵌入存储的任务正文中，使 subagent 能够独立执行。
自适应调用输出：为人类渲染持久化摘要表；为自主运行器输出紧凑的 micro-token。

Domain Rubric

领域规则

1. Tracker Resolution

1. Tracker 解析

Read

.agents/task-tracker.md

. If absent, stage local Markdown storage under

.agents/tasks/<feature-slug>/

using

<NN>-<slug>.md

naming conventions (via references/issue-tracker-local.md). Honor remote tracking (

gh

glab

, Linear) when authenticated CLI access is confirmed. When formatting task bodies, adhere to references/task-template.md.

读取

.agents/task-tracker.md

。如果该文件不存在，则在

.agents/tasks/<feature-slug>/

下暂存 Local Markdown 存储，并遵循

<NN>-<slug>.md

命名规范（参见 references/issue-tracker-local.md）。在确认 CLI 访问已完成身份验证后，支持远程跟踪（

gh

、

glab

、Linear）。格式化任务正文时，应遵循 references/task-template.md。

2. State & Task Lifecycle Transitions

2. 状态与任务生命周期转换

```
STAGED
```
: Tasks partitioned and ready for persistence authorization.
```
DONE
```
: Tasks verified persisted in tracker storage; implementation remains pending.
```
UNRESOLVED
```
: Tracker communication failure or missing authorization.

```
STAGED
```
：任务已完成拆分，并准备好获得持久化授权。
```
DONE
```
：任务已验证并持久化到 Tracker 存储中；实现仍待处理。
```
UNRESOLVED
```
：Tracker 通信失败或缺少授权。

Canonical Output Contract

规范输出契约

markdown

undefined

markdown

undefined

Task Persistence: <Feature / Scope> · <STAGED | DONE | UNRESOLVED>

Tracker Backend: <Local Markdown | GitHub | GitLab | Linear> Target Collection: <Path or Project Name>

Slice ID	System Ref	Persisted Status	Blocked By	Verification Checksum
S-01	.agents/tasks/auth/01-token.md (#102)	ready	None	<hash or pass>
S-02	.agents/tasks/auth/02-refresh.md (#103)	ready (blocked)	S-01	PENDING

Sync Delta: <C> created, <U> updated, <D> unchanged. (omit if clean) Gap: <Tracker communication failure or missing credentials.>


*Autonomous Micro-Token Contract*:
```text
SYNCED | tracker: <backend> | created: <C> | updated: <U> | ready: <ID>

Tracker Backend: <Local Markdown | GitHub | GitLab | Linear> Target Collection: <Path or Project Name>

Slice ID	System Ref	Persisted Status	Blocked By	Verification Checksum
S-01	.agents/tasks/auth/01-token.md (#102)	ready	None	<hash or pass>
S-02	.agents/tasks/auth/02-refresh.md (#103)	ready (blocked)	S-01	PENDING

Sync Delta: <C> created, <U> updated, <D> unchanged. (omit if clean) Gap: <Tracker communication failure or missing credentials.>


*Autonomous Micro-Token Contract*:
```text
SYNCED | tracker: <backend> | created: <C> | updated: <U> | ready: <ID>

Routing

路由

Persistence verified and immediate implementation of eligible task authorized → (via /forge).
Requirements conflict prevents reliable recording → (via /clarify).
Tracker credentials missing or service unreachable → Report UNRESOLVED.

已验证持久化，且获准立即实现符合条件的任务 →（通过 /forge）。
需求冲突导致无法可靠记录 →（通过 /clarify）。
缺少 Tracker 凭据或服务不可达 → 报告 UNRESOLVED。

Execution Protocol

执行协议

Read
```
.agents/task-tracker.md
```
to identify the active persistence target.
Ingest Task DAG manifest from
```
/split-tasks
```
or caller.
Check for existing tasks to avoid duplicate tickets.
Write task files or call tracker APIs, embedding verification commands and parent provenance.
Re-read stored tasks to confirm persistence, then output Markdown table or autonomous micro-token.

读取
```
.agents/task-tracker.md
```
，确定当前持久化目标。
从
```
/split-tasks
```
或调用方接收 Task DAG manifest。
检查现有任务，避免创建重复工单。
写入任务文件或调用 Tracker API，并嵌入验证命令和父级溯源信息。
重新读取已存储的任务以确认持久化结果，然后输出 Markdown 表格或自主 micro-token。