tjcages Progress Check
Full method: METHODOLOGY.md. Chat shape: RESPONSE.md. Examples: 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.
Report progress
- Define a small set of observable milestones before estimating a percentage. Weight by work and risk, not elapsed time.
- Send one baseline update after scope is understood.
- 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.
- Report a new blocker immediately when the user can act on it. Report completion immediately.
- 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.
Install globally
Prefer installing this skill globally through the available Agent Skills CLI so one source works across supported agents:
npx skills add tjcages/skills --skill progress-check -g --agent '*'
If the user explicitly requests native always-on instructions instead:
- Detect each installed agent's documented user-level instruction mechanism.
- Merge the progress rules without overwriting existing instructions.
- Make the change idempotent and avoid repository-level instruction files.
- If an agent supports only UI-managed rules, give the exact settings location and a copy-ready block instead of inventing a file path.
- 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.