TESP

Apply TESP whenever silence would create coordination risk.

中文简介

TESP（Task Execution Signal Protocol / 任务执行信号协议）是一套面向非即时任务的执行治理协议。

它的核心不是“把任务做完”本身，而是让执行过程对协作者可见、可查、可监督。

适用于研究、迁移、排查、实施、跨 agent 协作、异步任务和任何需要持续推进但不能静默消失的工作。

What this skill is for

TESP turns long or multi-step work into a visible execution flow.

It is for tasks that need acknowledgement, staged progress, blockers, active task tracking, and clean handoff discipline.

Typical triggers:

• “Do this and keep me posted.”
• “Break this big task down and supervise execution.”
• “Set a working protocol so I don’t need to chase status.”
• “Audit whether agents are actually following the execution standard.”
• “Clean up the task board so only current work stays visible.”

Core operating sequence

Follow this order:

1. Acknowledge fast — send Layer 1 with visible TESP version, scene, and goal.
2. Stage the work — if the task is long, split it into numeric progress units like 2/5.
3. Broadcast by cadence — update based on expected duration, not random chatter.
4. Track active work — keep current tasks in TASK_QUEUE.md.
5. Archive finished work — move completed items into TASK_ARCHIVE.md.
6. Escalate blockers clearly — say what is blocked and what decision is needed.
7. Keep audits cheap — prefer file checks, diffs, and samples over full replay.

Minimum operating requirements

For any non-instant task:

• Use Layer 1 acknowledgement with visible TESP version.
• Use numeric progress for long tasks.
• Keep active and completed work separated.
• Do not make the human chase status.

Multi-agent rule

When multiple agents are involved:

• update the task board first
• write the shared handoff second
• then transfer execution

Model rule

Use GLM / MiniMax by default for lightweight governance, queue checks, and audits.

Upgrade only when stronger reasoning is actually needed.

Read next

For the full protocol text and exact templates, read:

• references/protocol.md
• references/templates.md