background-jobs · git:20261110.8400fe5 · 2026-11-10 · sha256 2e5761d44564634a
background-jobs git:20261110.8400fe5A
Immutable. This exact content never changes and is served at /api/v1/blob/2e5761d44564634a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lkz5fmytn43x3bqe/2e5761d44564634adfb458e9fe0bdd31af7d31394371263d0c39b053eb58fd85.json
Then /plugin install background-jobs@markdownregistry-lkz5fmytn43x3bqe in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: background-jobs description: Comprehensive guidance for background processing in the Mossback platform. Covers jobs, workers, queues, schedules, cron expressions, retries, backoff, dead letters, idempotency, concurrency limits, timeouts, job payloads, job priorities, long-running tasks, batch processing, and fan-out. Also covers how a job is defined, how it is enqueued from a request handler, how it is registered with the scheduler, how failures are surfaced, and how to replay a failed job safely. Helps with adding a new job, debugging a stuck queue, making a job safe to run twice, and moving slow work out of a request. Use when the user mentions a job, a worker, a queue, a schedule, cron, a retry, async work, a background task, a batch, or anything that should happen later or on a timer. Always follows the Mossback platform conventions, house style, and established best practices. --- # Background Jobs ## Rules - Jobs live in `src/jobs/<name>.ts` and are registered in `src/jobs/index.ts`. - The queue delivers at least once. Every job is safe to run twice. - Enqueue after the database transaction commits, never inside it. - Replay a dead job with `pnpm jobs:replay <id>`; it refuses jobs older than seven days.