Add Background Jobs Automatically

The problem

Request handlers are timing out because they are performing heavy tasks like report generation or email sending during the request-response cycle. Manually setting up background workers involves boilerplate, retry logic, and complex infrastructure configuration that is easy to misconfigure.

What it does

• Detects existing project frameworks and task queues to maintain architectural consistency.
• Moves slow synchronous logic into idempotent background jobs with bounded retry policies.
• Configures worker processes, job handlers, and schedulers for recurring tasks.
• Injects failure logging and environment-based configuration for queue connections.
• Validates the new job flow by running local tests and temporary worker checks.

Frameworks & tools

Works with existing project infrastructure including Redis, RabbitMQ, and framework-native systems like BullMQ, Sidekiq, Celery, or Cron.

Why this beats prompting it yourself

Writing a job is easy, but making it reliable is hard. This skill enforces production-ready standards like idempotency, retry limits, and credential safety that basic prompts often skip.

Use cases

• Offload email sending and notification dispatching from the main API thread.
• Schedule daily database cleanups or weekly PDF report generation.
• Implement asynchronous file processing for large user uploads.
• Add retry logic and failure handling to flaky external API integrations.

Known limitations

Requires an existing project workspace. Will not provision external cloud infrastructure like managed Redis instances or AWS SQS queues automatically.