← ClaudeAtlas

evidence-led-concurrency-and-deliverylisted

Review, design, implement, or debug reliability-critical asynchronous or concurrent execution when the task concerns cancellation, failure isolation, ownership, durability, idempotency, backpressure, fairness, or graceful shutdown. Do not use for ordinary concurrency syntax or unrelated performance tuning.
rachmanzz/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill rachmanzz/skills
# Evidence-Led Concurrency and Delivery Use this skill when the requested work concerns lifecycle or delivery guarantees, failure boundaries, overload behavior, or recovery of asynchronous or concurrent execution. Do not invoke it merely because an implementation uses threads, tasks, workers, callbacks, or asynchronous syntax. The goal is to make claimed behavior explicit and verifiable within a stated scope across languages, runtimes, storage systems, and deployment models. This skill is product-agnostic and language-agnostic. Use the repository's actual terminology only after mapping it to neutral concepts such as work item, executor, delivery backend, durable storage, ownership period, and completion acknowledgement. Do not assume that similarly named mechanisms have equivalent semantics. Read only the references needed for the current task: - Read [evidence-and-assumption-control.md](references/evidence-and-assumption-control.md) before making claims about existing behavior, completed work, or guarantees. - Read [cancellation-and-failure-propagation.md](references/cancellation-and-failure-propagation.md) for cancellation, timeout, error propagation, and child-work boundaries. - Read [panic-recovery-and-leak-prevention.md](references/panic-recovery-and-leak-prevention.md) for failure isolation, cleanup, and leaked execution or resources. - Read [join-wait-and-shutdown.md](references/join-wait-and-shutdown.md) for join/wait contracts, draining, and bounded grace