# Forge Jobs

> Inspect queued and scheduled work for durability, idempotency, retries, poison messages, and operability.

- Skill: `is-bo/forge-jobs-3` (Agent Skill)
- Install (CLI): `npx skillmds@latest add is-bo/forge-jobs-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/is-bo/forge-jobs-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: is-bo (https://skillmd.com/u/is-bo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/is-bo/forge-jobs-3

---


# forge-jobs: Background jobs

Engine: Forge native

## Purpose

Inspect queued and scheduled work for durability, idempotency, retries, poison messages, and operability.


## Deterministic runtime composition

Before loading any provider procedure, run:

Resolve `../../runtime/cli/src/composition-entry.js` relative to this `SKILL.md`, then run:

`node "<resolved-absolute-runner-path>" jobs compose --workflow audit --root "<repository-root>" --dry-run --json`

Add one repeatable `--request <provider-or-source>` flag for each explicit user request. Add
`--condition <task-condition>` or `--risk-surface <surface>` only for a task fact you directly
proved; never infer one from generic wording. The command above is the default for this
audit-oriented module; for implementation use `--workflow build`, and for a fix, retest, or
release gate use `--workflow fix`, `verify`, or `ship` respectively. Read the JSON response,
keep the Forge contract at index zero, and resolve paths against the absolute `runtime_root`
reported in that response. Read `eager[].runtimePath` when entering the module. The full
`selected[]` list is availability/provenance; load only `deferred[].runtimePath` when the task
reaches that concern, in tier order. Refuse any path that escapes the root. Respect every reported
suppression and context budget. If `missing` is non-empty, stop and report the installation as
damaged; do not improvise a prose fallback. The runner and specialist content may live in a plugin
cache or global installation; never assume they are inside the audited repository.


Resolve and read `../fullstack-forge/references/shared/module-contract.md` (applicability,
execution, mutation, verification, completion) and
`../fullstack-forge/references/shared/evidence-rules.md` (statuses, standards, tools, findings via
`../fullstack-forge/references/PROTOCOL.md`) relative to this module `SKILL.md` before reporting.

Never hide failed checks or claim that an operation ran when it did not.

## Automatic activation signals

Activate when a request or direct repository evidence involves background jobs, when
the user explicitly names `forge-jobs`, or when discovery proves an applicable boundary.

- Queues, workers, cron, scheduled functions, and outbox consumers

## When not to activate

- Applications with no asynchronous or scheduled execution

## Automated support

Relevant discovery inputs are:

- queue and scheduler configuration
- producers and consumers
- job tests

Deterministic support, bounded evidence only:

- `inspect-routes`

## Agent inspection procedure

1. Inventory queues, workers, and scheduled jobs with their triggers, and trace one job from enqueue to completion including the failure path.
2. Verify idempotency: determine what happens when the same job runs twice, concurrently, or after a partial failure.
3. Inspect retry policy, backoff, limits, and the destination of permanently failing jobs (dead-letter or silent loss).
4. Check transaction boundaries: whether enqueue happens atomically with the state change that requires it (outbox or equivalent).
5. Verify observability: how an operator would find a stuck queue, a poison message, or a job that never ran, and how deploys interact with in-flight jobs.

Manual inspection requirements:

- Review operational replay and poison-message runbooks
- Confirm provider retention and retry settings outside the repository

Stack-specific guidance:

- Use provider-native acknowledgement and visibility-timeout semantics

## Evidence to collect

Standards used as criteria:

- CloudEvents concepts
- NIST SSDF

## Common production failures

- Trace enqueue-to-effect flow and delivery guarantees
- Inspect idempotency keys, leases, timeouts, retries, jitter, dead-letter handling, ordering, concurrency, and payload versioning
- Verify transaction boundaries, outbox/inbox behavior, observability, replay, and shutdown

## Missing-control checks

Each item needs direct evidence or one reasoned status.

- Job idempotency
- Duplicate execution
- Retry limits
- Exponential backoff
- Dead-letter handling
- Timeouts
- Scheduling
- Concurrency
- Ordering
- Partial failures
- Transaction boundaries
- Poison messages
- Cancellation
- Progress reporting
- Safe deployment while jobs run
- Job observability
- Queue saturation
- Backpressure
- Email, invoice, image, reconciliation, report, notification, and import jobs

## Commands and tools

- Run `forge jobs audit --json` or `fullstack-forge jobs audit --json` when
  an explicit audit is requested and the CLI is installed. Normal feature work does not require it.

## Safe fixes

- Add bounded retry metadata, structured job logging, and payload validation
- Add tests for duplicate delivery

## Approval-required changes

- Introducing a queue or changing delivery and ordering semantics

## Verification

- Deliver the same job twice and observe one durable outcome
- Force failure through retry and dead-letter paths

## Completion contract

Follow `fullstack-forge/references/shared/completion.md` and the limitations below.

## Known limitations

- Managed queue policy is NOT_VERIFIED without configuration output