This skill should be used when the user designs a "task scheduler", "job scheduler", "job queue", "cron at scale", "distributed cron", "delayed / scheduled / recurring tasks", a "worker pool", reaches for "Celery / Sidekiq / Airflow", or wrestles with "task leasing", visibility timeouts, job priorities, fairness, or duplicate task execution. Use it whenever work must run later, on a schedule, or be reliably leased to a pool of workers, even if the user doesn't say "scheduler". (For plain queue transport and delivery guarantees, that is messaging-streaming.)
$npx -y skills add proyecto26/system-design-skills --skill task-schedulingInstalls into the current project.
Run `npx skills use "https://github.com/proyecto26/system-design-skills" --skill "proyecto26/system-design-skills/task-scheduling"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/proyecto26/system-design-skills" that are relevant to the current task. Run `npx skills add "https://github.com/proyecto26/system-design-skills"` and select the relevant skills, then follow their instructions.