workflow_explainer

Translates Rierino Saga JSON configurations into plain-language workflow explanations.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill workflow-explainer-rierino-open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow_explainer
Source: https://github.com/rierino-open/rierino-claude-plugin/tree/main/development/skills/workflow_explainer
Command: npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill workflow-explainer-rierino-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Saga workflow configurations on the Rierino platform are stored as dense JSON graphs that are difficult for developers and business stakeholders to interpret. This Skill reads those configurations and produces clear, human-readable documentation of what each workflow actually does. ## Core Features & Use Cases - Saga Explanation: Fetches a saga via the Rierino MCP server and explains its trigger, inputs, outputs, and every step in execution order. - Branching & Data Flow Analysis: Traces CONDITION branches, SUCCESS/FAIL routing, and how data moves between steps, including error paths. - Resource Enrichment: Fetches referenced query definitions and handler code so steps are explained by actual behavior, not just field names. - Use Case: A product manager asks "what does the order fulfillment saga do?" and receives a structured walkthrough covering validation, inventory checks, stock reservation, shipment creation, and failure handling in plain language. ## Quick Start Ask the assistant to explain what a specific saga does by providing its saga ID from the Rierino platform.

Frequently Asked Questions about workflow_explainer

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

FAQPage Schema
How do I explain what a Rierino saga does?▼

Provide the saga ID and the skill fetches the configuration using the State_Get_saga_write tool on the Rierino MCP server. It then walks through every step in graph order, explaining handlers, conditions, and data flow in plain language.

How to document a saga workflow for non-technical stakeholders?▼

The skill generates an overview, trigger details, input/output expectations, and a numbered step-by-step walkthrough written for business readers. Raw JSON is only included if explicitly requested.

Does the workflow explainer fetch referenced queries and handlers?▼

Yes, it fetches query definitions and handler code referenced by saga steps using State_Get tools before writing the explanation. If a fetch fails, it notes the gap and describes the step from available metadata.

Can it trace branching and error handling in a saga?▼

Yes, it follows graph links from the START node, explains each CONDITION branch separately, and describes SUCCESS/FAIL routing. It also flags any paths that do not terminate at a FINISH or FAIL node.

What information is needed to explain a saga?▼

You need the saga's ID on the Rierino platform. The skill asks for it if not provided, then retrieves the configuration and supporting resources through the authenticated Rierino MCP connection.