Progress Check

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.

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.

Performance rollout  [██████████████████░░] 90%

• 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.

Install globally

npx skills add tjcages/skills --skill progress-check -g --agent '*'

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.