Back to Details

progress-check

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Progress Check

进度检查

Full method: METHODOLOGY.md. Chat shape: RESPONSE.md. Examples: EXAMPLES.md.
完整方法：METHODOLOGY.md。对话模板：RESPONSE.md。示例：EXAMPLES.md。

Choose the mode

选择模式

  • Report progress: default for qualifying long-running work.
  • Install globally: only when the user asks to persist this behavior across agents or projects.
  • 进度汇报： 符合条件的长期工作默认使用此模式。
  • 全局安装： 仅当用户要求在所有Agent或项目中保持此行为时使用。

Report progress

进度汇报

  1. Define a small set of observable milestones before estimating a percentage. Weight by work and risk, not elapsed time.
  2. Send one baseline update after scope is understood.
  3. Send a routine update only when at least 30 minutes have passed and one of these is true: a milestone completed, verified progress rose by at least 10 percentage points, or the next action materially changed.
  4. Report a new blocker immediately when the user can act on it. Report completion immediately.
  5. Never repeat an unchanged bar or send a routine “still working” message.
Keep each update to at most three short items: completed evidence, current work, and next step or blocker. End with exactly one overall bar styled as inline code on its own line:
Performance rollout  [██████████████████░░] 90%
Use one pair of backticks for inline-code styling. Do not indent the line by four spaces and do not use a fenced code block; both create a separate block that interfaces may label or make copyable.
  • Replace the label with a short task-specific label.
  • Use 20 cells: 
    █
    completed and 
    ░
    remaining.
  • Round down to the nearest 5% unless completion evidence supports 100%.
  • Show only the overall bar unless the user requests subtask bars.
  • In multi-agent work, only the coordinator shows the overall bar.
  • The progress line is the final content in the update. End immediately after it with no note, recap, or closer.
  1. 在估算进度百分比前，先定义少量可观测的里程碑。根据工作量和风险而非耗时来加权。
  2. 在明确工作范围后发送一次基准更新。
  3. 仅当至少过去30分钟，且满足以下任一条件时才发送常规更新：完成一个里程碑、已验证的进度提升至少10个百分点，或下一步操作发生实质性变化。
  4. 当用户可以采取行动解决新障碍时，立即汇报。完成工作后立即汇报。
  5. 切勿重复发送无变化的进度条，也不要发送常规的“仍在工作中”消息。
每次更新最多包含三个简短条目：已完成的证据、当前工作内容，以及下一步计划或障碍。结尾必须是一行独立的内联代码格式的整体进度条：
Performance rollout  [██████████████████░░] 90%
使用一对反引号进行内联代码格式化。不要将该行缩进四个空格，也不要使用围栏代码块；这两种方式都会生成一个独立块，界面可能会对其添加标签或设置为可复制。
  • 将标签替换为简短的任务专属标签。
  • 使用20个单元格：
    █
    代表已完成，
    ░
    代表未完成。
  • 除非有完成证据支持100%，否则向下取整到最接近的5%。
  • 除非用户要求显示子任务进度条，否则仅展示整体进度条。
  • 在多Agent协作工作中，仅由协调者展示整体进度条。
  • 进度条行是更新的最后内容。其后无需添加注释、回顾或结束语，直接结束。

Install globally

全局安装

Prefer installing this skill globally through the available Agent Skills CLI so one source works across supported agents:
bash
npx skills add tjcages/skills --skill progress-check -g --agent '*'
If the user explicitly requests native always-on instructions instead:
  1. Detect each installed agent's documented user-level instruction mechanism.
  2. Merge the progress rules without overwriting existing instructions.
  3. Make the change idempotent and avoid repository-level instruction files.
  4. If an agent supports only UI-managed rules, give the exact settings location and a copy-ready block instead of inventing a file path.
  5. Verify each changed target and state whether a new session is required.
Do not claim an unsupported agent was configured. Do not modify unrelated preferences.
优先通过可用的Agent Skills CLI全局安装此技能，以便在所有支持的Agent中统一使用：
bash
npx skills add tjcages/skills --skill progress-check -g --agent '*'
如果用户明确要求使用原生的始终启用指令，则按以下步骤操作：
  1. 检测每个已安装Agent的文档中记载的用户级指令机制。
  2. 合并进度规则，不要覆盖现有指令。
  3. 确保修改具有幂等性，避免修改仓库级别的指令文件。
  4. 如果某个Agent仅支持UI管理的规则，请提供确切的设置位置和可直接复制的内容块，而非自行编造文件路径。
  5. 验证每个修改目标，并说明是否需要启动新会话。
不要声称已配置不支持的Agent。不要修改无关的偏好设置。