workflow-gateway-slice-sequencing

Plans isolation of workflow gateway UI changes from runtime execution logic.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-gateway-slice-sequencing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-gateway-slice-sequencing
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.squad/skills/workflow-gateway-slice-sequencing
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-gateway-slice-sequencing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the architectural risk of introducing complex workflow gateway logic by decoupling visual representation from runtime execution semantics.

Core Features & Use Cases

  • Visual-First Implementation: Allows developers to introduce split and join gateway UI elements into the workflow editor without prematurely altering the underlying execution engine.
  • Behavioral Slicing: Provides a structured approach to implementing concurrent execution by separating authoring contracts from engine-level state machine changes.
  • Use Case: When a team needs to add complex branching to a service blueprint, this skill ensures the editor reflects the new gateways immediately while keeping the runtime execution stable until the engine is ready for concurrent processing.

Quick Start

Use the workflow-gateway-slice-sequencing skill to generate a plan for isolating gateway UI changes from runtime execution logic in the current project.

Frequently Asked Questions about workflow-gateway-slice-sequencing

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

FAQPage Schema
How do I add split and join gateway UI elements to a workflow editor without breaking runtime execution?

To add split and join gateway UI elements safely, decouple the visual representation from runtime execution semantics. This approach updates the editor immediately while keeping the state machine execution stable until the engine supports concurrent processing.

What is workflow gateway slice sequencing for complex state machine development?

Workflow gateway slice sequencing is a behavioral slicing pattern that manages incremental implementation of concurrent execution. It separates authoring contract tests from engine-level state machine changes to safely introduce split and join logic.

How do I incrementally introduce concurrent execution paths into an existing stage-driven workflow?

Introduce concurrent execution incrementally by applying behavioral slicing patterns and pinning authoring contract tests. This method decouples editor visual updates from engine-level state machine changes, ensuring existing execution paths remain unbroken.

When do I need to decouple workflow editor UI logic from the underlying state machine runtime?

Decoupling workflow editor UI logic from runtime is needed when adding complex branching to a service blueprint. It allows the editor to reflect new gateways immediately while keeping runtime execution stable until the engine is ready for concurrent processing.

What are the limitations of introducing complex gateway logic without behavioral slicing patterns?

Without behavioral slicing patterns, introducing complex gateway logic risks breaking existing stage-driven execution paths. Neglecting to pin authoring contract tests during state machine development can cause runtime execution semantics to destabilize prematurely.