Feishu Progress Heartbeat

Use this skill when a Feishu task should continue to feel alive after it has
been spawned or delegated.

Goal

Turn long-running work into a visible flow:

1. 1. immediate acknowledgement
2. background execution
3. automatic progress heartbeat every 3 minutes while still running
4. final result when finished

Where it applies

• - INLINECODE0
• INLINECODE1
• INLINECODE2
• INLINECODE3
• INLINECODE4
• INLINECODE5
• INLINECODE6

Required behavior

When a heartbeat fires and there are still active tasks in the current Feishu
session:

1. 1. inspect active child tasks with sessions_list, subagents, or INLINECODE9
2. infer the most likely current stage for each active task
3. send a short progress update back to the same Feishu conversation
4. include an estimated percentage for each task
5. if a task looks stalled, failed, or has shown no meaningful movement for two heartbeat cycles, send a blocker update instead of another generic progress line

If there is no active task, no meaningful state change, or no useful update,
reply HEARTBEAT_OK.

If there is no active child task and no fresh continuation branch was launched,
do not emit a fake progress update just to sound alive.

Do not expose internal session inspection details, raw tool payloads, or
command objects in a heartbeat reply. Only send the user-facing status line.

Percentage mapping

Use short stage labels and one estimated percentage:

• - 已接单 -> INLINECODE12
• INLINECODE13 -> INLINECODE14
• INLINECODE15 / 收集资料中 -> INLINECODE17
• INLINECODE18 / 分析中 -> INLINECODE20
• INLINECODE21 / 写作中 / 制作 PPT 中 -> INLINECODE24
• INLINECODE25 -> INLINECODE26
• INLINECODE27 / 长时间无进展 -> INLINECODE29
• INLINECODE30 / 准备回复 -> INLINECODE32
• INLINECODE33 -> INLINECODE34
• INLINECODE35 -> INLINECODE36

These numbers are estimates. Say so naturally when helpful, but do not over-explain.

Reply format

Prefer Feishu-friendly short lines:

• - INLINECODE37
• INLINECODE38
• INLINECODE39
• INLINECODE40
• INLINECODE41

If several tasks are running, keep the list compact and readable.

Guardrails

• - Do not send heartbeat updates for tiny tasks that already finished quickly.
• Do not invent exact progress meters; use stage-based estimates.
• Do not spam if nothing meaningful changed.
• If a task is blocked, say what it is waiting on in one short clause.
• Do not repeat the same optimistic progress line forever.
• If the stage is unchanged for two heartbeat cycles, treat it as a stall candidate and surface a blocker or fallback action.
• Do not send meta lines like "我先检查一下当前任务状态". Do the check first, then send the result.
• Do not send a percentage-only progress claim unless there is actual evidence

Pairing

Use together with:

• - INLINECODE42
• INLINECODE43
• INLINECODE44 when one task becomes a task tree