async-task-platform-specialist

Guide Redis-backed distributed delay queue architecture with scheduling, retries, and lifecycle management.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/AkikoAkaki/async-task-platform --skill async-task-platform-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: async-task-platform-specialist
Source: https://github.com/AkikoAkaki/async-task-platform/tree/main/.agent/skills/distributed-delay-queue-specialist
Command: npx skills add https://github.com/AkikoAkaki/async-task-platform --skill async-task-platform-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides expert guidance for building and maintaining a Redis-backed distributed delay queue (DDQ) system, covering scheduling, worker pools, retries, and lifecycle management.

Core Features & Use Cases

  • Delay storage: Redis Sorted Set (ZSET) with scores as target timestamps.
  • Atomic fetch: Lua script to atomically fetch and move jobs into a processing state.
  • Retry & DLQ: Exponential backoff and Dead Letter Queue handling for failed tasks.
  • Watchdog: Monitoring and auto-recovery for stuck tasks.
  • Job lifecycle: PENDING, ACTIVE, COMPLETED, and FAILED transitions.
  • Observability & scaling guidance for production deployments.

Quick Start

Design and implement a DDQ deployment plan by outlining delay storage, fetch, retry, and worker coordination steps.

Frequently Asked Questions about async-task-platform-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Redis-backed distributed delay queue for scheduled tasks?

Build a distributed delay queue using Redis Sorted Sets for delay storage and Lua scripts for atomic job fetching. This ensures reliable scheduling by moving jobs through PENDING, ACTIVE, and COMPLETED states without race conditions.

How does atomic fetch prevent race conditions in a distributed delay queue?

Atomic fetch in a distributed delay queue uses a Lua script to simultaneously fetch and transition jobs into the ACTIVE state. This prevents multiple workers from pulling the same scheduled task from Redis concurrently.

What is the best way to handle retries and failed tasks in a Redis delay queue?

Handle retries in a Redis delay queue using exponential backoff for rescheduling failed tasks. Jobs that exhaust retries are routed to a Dead Letter Queue, ensuring persistent failures are isolated without blocking active workers.

How do I monitor and recover stuck tasks in a distributed delay queue system?

Recover stuck tasks in a distributed delay queue by implementing a watchdog system. The watchdog monitors ACTIVE jobs that exceed their expected processing time and automatically resets their state for re-processing.

Can I scale worker pools dynamically in a Redis-based distributed delay queue?

Yes, you can scale worker pools in a Redis-based distributed delay queue. The architecture supports adding or removing workers dynamically because the atomic fetch mechanism coordinates job distribution centrally through Redis.

What are the production observability requirements for a distributed delay queue?

Production observability for a distributed delay queue requires tracking job lifecycle transitions, monitoring worker pool throughput, and alerting on DLQ accumulation. This ensures reliable operation and identifies scaling bottlenecks in the Redis backend.