scheduled-taskslisted

# Scheduled Tasks Schedule recurring or one-shot prompts using Claude Code's built-in cron tools. ## When to Use - Poll CI/CD pipeline status at intervals - Set reminders during long-running work - Periodic quality checks (lint, test, build) - Monitor external resources or services - Recurring data collection or reporting ## When NOT to Use a Cron `CronCreate` re-runs a prompt at fixed wall-clock intervals. It is the wrong instrument for short waits and live watching — cron polls on a schedule and cannot fire mid-query, so it will not notice an event until its next tick. Reach for these instead: | Need | Instrument | |------|-----------| | **One** notification when a condition becomes true ("tell me when the build finishes", "when the server is ready") | `Bash` with `run_in_background`, running a command that exits once the condition holds: `until grep -q "Ready in" dev.log; do sleep 0.5; done` | | **One per occurrence**, as it happens ("tell me every time an ERROR line appears") | `Monitor` — each stdout line of a long-running script becomes an event, streamed in real time | | **One per occurrence until a known end** (emit each CI step, stop when the run completes) | `Monitor` with a command that emits lines and then exits | | Waiting a few seconds or minutes inside a task | `Monitor` with an until-loop — foreground `sleep` is blocked in `Bash` | | Anything that must outlive the session | `RemoteTrigger` (`remote-triggers` skill) | Use a cron only for genuinely period