queue-design-generator

Generates BullMQ queue architecture specifications from API, service, and business logic designs.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/fen-zx/NovelToScript --skill queue-design-generator-fen-zx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: queue-design-generator
Source: https://github.com/fen-zx/NovelToScript/tree/main/.agents/skills/queue-design-generator
Command: npx skills add https://github.com/fen-zx/NovelToScript --skill queue-design-generator-fen-zx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing asynchronous task infrastructure for backend systems is error-prone and time-consuming. This Skill automates the creation of a complete BullMQ queue architecture document (QUEUE_SPECS.md) from existing API specs, service designs, or business logic descriptions, ensuring consistent retry, timeout, and monitoring strategies. ## Core Features & Use Cases - Automatic Queue Identification: Scans business logic to detect time-consuming tasks (AI generation, file export, batch processing) and maps them to dedicated Queues, Jobs, and Workers. - Complete Reliability Design: Produces task state machines (PENDING/PROCESSING/COMPLETED/FAILED), retry policies with exponential backoff, timeout limits, and priority strategies. - AI Project Special Rules: Detects Novel/Script/Character/Scene entities and generates a tailored pipeline (generate-script → analyze-character → generate-scene → save-script). - Use Case: Given a SERVICE_SPECS.md describing generateScript() and exportPdf(), the Skill outputs a full QUEUE_SPECS.md with Job interfaces, Worker responsibilities, Redis key design, monitoring metrics, and risk analysis. ## Quick Start Ask the AI to generate a BullMQ queue design document from your SERVICE_SPECS.md or API_SPECS.md file.

Frequently Asked Questions about queue-design-generator

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

FAQPage Schema
How do I design a BullMQ queue architecture for my backend?▼

Provide your API specs, service design, or business logic document as input. The Skill identifies time-consuming tasks and generates a QUEUE_SPECS.md covering Queues, Job interfaces, Workers, retry policies, timeouts, priorities, and monitoring design.

What tasks should use BullMQ queues instead of synchronous processing?▼

Use queues for AI generation, file export, upload parsing, and batch operations. Simple CRUD, basic queries, and synchronous business logic should not be queued, as the Skill explicitly excludes these from queue design.

Does the queue design include retry and timeout strategies?▼

Yes. The output includes retry policies with exponential backoff (e.g., attempts: 3), per-queue timeout limits (e.g., 600s for script generation, 120s for PDF export), and a unified task state machine covering PENDING through FAILED states.

Can BullMQ handle AI novel-to-script generation pipelines?▼

Yes. When Novel, Script, Character, or Scene entities are detected, the Skill generates a specialized pipeline: generate-script, analyze-character, generate-scene, and export-pdf queues with defined execution order and error codes like AI_TIMEOUT.

What are the limitations of this queue design approach?▼

The Skill produces design documentation only, not executable Worker code. It forbids synchronous AI execution, direct HTTP access from Workers, and storing large text payloads in Jobs; unknown details are marked as [待确认] for manual confirmation.