step-functions

Design AWS Step Functions state machines for multi-step process orchestration.

15|20|Updated May 11, 2026
One-click install
npx skills add https://github.com/awslabs/startups --skill step-functions-awslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step-functions
Source: https://github.com/awslabs/startups/tree/main/solution-architecture/plugins/aws-dev-toolkit/skills/step-functions
Command: npx skills add https://github.com/awslabs/startups --skill step-functions-awslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams design reliable AWS Step Functions workflows by providing guidance for orchestrating complex processes, handling failures, and selecting the right workflow execution model.

Core Features & Use Cases

  • Workflow Design Guidance: Create state machines using best practices for Standard and Express workflows, state types, and data processing patterns.
  • Reliability Patterns: Implement retries, catches, saga compensations, human approval callbacks, and distributed processing strategies.
  • AWS Service Integration: Build workflows using direct integrations with services like DynamoDB, SQS, EventBridge, ECS, and Bedrock instead of unnecessary Lambda wrappers.
  • Use Case: Design an order processing workflow that charges payments, reserves inventory, ships products, and automatically compensates completed steps when failures occur.

Quick Start

Use the step-functions skill to design a production-ready AWS Step Functions workflow for processing customer orders with retries, error handling, and compensation steps.

Frequently Asked Questions about step-functions

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

FAQPage Schema
How do I orchestrate a saga pattern with rollback compensations in AWS Step Functions?

AWS Step Functions state machines orchestrate saga transactions by defining compensation steps that automatically trigger on failure, rolling back completed actions like payment charges or inventory reservations to maintain data consistency across distributed services.

What's the best way to handle errors and retries in serverless workflow orchestration?

Serverless workflow orchestration with AWS Step Functions handles errors by configuring retry policies with exponential backoff and catch blocks that route failures to fallback states, ensuring reliable execution of multi-step processes without manual intervention.

When should I use Standard vs Express workflows for state machine architecture?

Standard workflows suit long-running, auditable orchestrations with distributed processing and human approval callbacks, while Express workflows handle high-volume, short-lived event-driven automation requiring rapid invocation and lower latency execution.

Do I need Lambda functions to integrate AWS Step Functions with DynamoDB and SQS?

AWS Step Functions supports direct service integrations with DynamoDB, SQS, EventBridge, ECS, and Bedrock, allowing you to read, write, and message between services directly without writing unnecessary Lambda wrapper functions.

How do I design a human approval workflow for processing customer orders?

Human approval workflows in AWS Step Functions use callback patterns with Amazon SQS or EventBridge to pause state machine execution, wait for external manual authorization, and resume the order processing pipeline upon receiving the approval callback.

Can AWS Step Functions coordinate parallel processing for multi-step application workflows?

AWS Step Functions coordinates parallel processing by using Parallel or Map states to execute multiple branches or iterate over collections simultaneously, accelerating multi-step application workflows while maintaining centralized error handling and state management.