skills.rest
erikshafer
erikshaferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wolverine-sagas

Manage long-running workflows in CritterCab using Wolverine sagas.

Updated Apr 21, 2026
Search Tags:#state management#sagas#wolverine#ride-sharing#long-running workflows
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-sagas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wolverine-sagas
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/wolverine-sagas
Command: npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-sagas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Wolverine, Marten, Polecat, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of implementing long-running, stateful workflows in CritterCab, leveraging Wolverine's saga capabilities for managing complex, multi-step processes.

Core Features & Use Cases

  • Long-Running Workflow Management: Handle workflows that span multiple steps, retries, and external systems.
  • Saga Persistence: Store and retrieve saga state using Marten or Polecat, ensuring durability across restarts.
  • Timeout Management: Schedule and manage timeouts for sagas, allowing for retries and event-driven execution.
  • Use Case: Coordinate a trip completion workflow across multiple bounded contexts, ensuring that pricing, payments, and ratings are processed correctly.

Quick Start

Use the wolverine-sagas skill to start a new saga for a ride request in CritterCab.

Frequently Asked Questions about wolverine-sagas

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

FAQPage Schema
How do I manage long-running workflows in a ride-sharing platform?▼

Wolverine sagas manage long-running workflows in ride-sharing platforms by coordinating multi-step processes like trip completion across pricing, payments, and ratings. This ensures stateful orchestration across external systems and bounded contexts with retries.

How does saga state persistence work with Wolverine?▼

Saga state persistence with Wolverine stores and retrieves workflow state using Marten or Polecat, ensuring durability across application restarts. This allows long-running workflows to resume correctly after failures or service restarts.

Do I need Marten or Polecat to use Wolverine sagas?▼

Yes, you need either Marten or Polecat for saga persistence support when using Wolverine sagas. These dependencies provide the required storage infrastructure to persist and retrieve state for long-running workflows.

What is the best way to schedule timeouts for long-running sagas?▼

Scheduling timeouts for long-running sagas is handled natively by Wolverine, allowing for retries and event-driven execution. This mechanism manages workflow delays and ensures steps resume after specified timeout periods.

When should I use sagas for state management instead of standard request handling?▼

Use sagas for state management when coordinating workflows that span multiple bounded contexts, require external system integration, or need timeout scheduling. Standard request handling is insufficient for these complex, long-running stateful processes.

Related Skills

Explore More Software Engineering Skills→
erikshafererikshafer

service-bootstrap

Configures CritterCab services with Wolverine, Marten/Polecat, and Aspire integration.

Community
Advanced
daemon-blockint-techdaemon-blockint-tech
7

microservices-developer

Guide teams in designing resilient microservices with clear boundaries and contracts.

Community
Advanced
erikshafererikshafer

wolverine-marten-automation

Automate committed domain event handlers in CritterCab using Wolverine and Marten.

Community
Advanced
erikshafererikshafer

dynamic-consistency-boundary

Implement Dynamic Consistency Boundary handlers for multi-stream consistency in .NET with Wolverine and Marten.

Community
Advanced