Background Job Playbook

HARD-GATE

• Idempotency key and error classification are documented before implementation.
• A failing worker test exists and fails for the right reason before perform/1 is written.
• perform/1 is a thin edge: fetch IDs → pure core → return tagged tuple.
• Failure paths are tested; user approves the worker design.
• mix format --check-formatted, mix credo --strict, and the full mix test suite are green before the PR is opened.

When to use

Adding or hardening Oban (or similar) background workers.

Atomic skills this playbook loads