workflows

Orchestrate asynchronous background tasks using SQS or Hatchet.

2.6k|238|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/useautumn/autumn --skill workflows-useautumn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows
Source: https://github.com/useautumn/autumn/tree/main/.claude/skills/workflows
Command: npx skills add https://github.com/useautumn/autumn --skill workflows-useautumn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates asynchronous background tasks using SQS or Hatchet to simplify job orchestration in backend services.

Core Features & Use Cases

  • SQS-based tasks: lightweight, fire-and-forget jobs with simple setup.
  • Hatchet-based workflows: complex, retry-enabled, multi-step tasks with typed outputs and observability.
  • Use Case: Trigger onboarding, billing, and data-sync processes as independent workflows processed by workers.

Quick Start

Steps to add a new workflow: define job names, register in the workflow registry, implement handlers, and trigger tasks using provided helpers.

Frequently Asked Questions about workflows

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

FAQPage Schema
How do I orchestrate async background tasks in a backend service?

You can orchestrate async background tasks by defining a typed payload, registering jobs in a workflow registry, and selecting a runner. This Skill uses SQS or Hatchet to simplify job orchestration for backend services requiring queue-based processing.

When should I use SQS versus Hatchet for queue-based jobs?

Use SQS for lightweight, fire-and-forget jobs with simple setup. Use Hatchet for complex, retry-enabled, multi-step tasks that require typed outputs and observability. Both runners support independent workflows processed by workers.

How do I add a new workflow to trigger background jobs?

To add a new workflow, define your job names, register them in the workflow registry, implement the handlers, and trigger tasks using provided helper utilities. This requires a typed payload and runner selection.

Can I process multi-step tasks with retries and typed outputs?

Yes, multi-step tasks with retries and typed outputs are supported through the Hatchet runner. It enables complex, retry-enabled workflows with built-in observability for backend services.

What use cases are supported for async task orchestration?

Common use cases include triggering onboarding, billing, and data-sync processes as independent workflows. These queue-based jobs are processed asynchronously by workers using either SQS or Hatchet.

Do I need a typed payload to queue background jobs?

Yes, a typed payload is required to queue background jobs. Along with a workflow registry and runner selection, the typed payload ensures reliable processing and observability for your asynchronous tasks.