workflow-gateway-behavioural-proof

Enforce gateway-only authoring models in workflow editor test suites.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the confusion caused by transition-first mental models in workflow editors, ensuring that the visual and functional logic of the workflow is correctly aligned with a stage-gateway-join architecture.

Core Features & Use Cases

  • Visual Geometry Validation: Proves that the canvas correctly renders as stage-to-gateway-to-node sequences rather than direct stage-to-stage jumps.
  • Product-Centric Testing: Enforces terminology that reflects the user experience, focusing on stages, gateways, and waiting messages.
  • Use Case: Use this when refactoring a workflow engine to ensure that your test suite accurately reflects the diamond-routing behavior of gateways and prevents the persistence of legacy transition-based logic.

Quick Start

Run the workflow-gateway-behavioural-proof skill to audit your current test suite for transition-first anti-patterns and align them with the gateway-only authoring model.

Frequently Asked Questions about workflow-gateway-behavioural-proof

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

FAQPage Schema
How do I test workflow routing logic to ensure it uses gateway patterns?

Workflow behavioral proof is a testing method that validates workflow logic by enforcing a gateway-only authoring model. It ensures visual and functional logic aligns with stage-gateway-join architecture rather than confusing transition-first patterns.

Why does my workflow UI allow direct stage-to-stage jumps instead of routing through gateways?

Direct stage-to-stage jumps occur because of transition-first mental models in workflow editors. Auditing your test suite for transition-first anti-patterns and aligning tests with a gateway-only authoring model eliminates this legacy logic.

How do I validate state machine UI canvas geometry during workflow refactoring?

You validate canvas geometry by applying behavioral proofs to confirm the editor renders stage-to-gateway-to-node sequences. This enforces strict adherence to stage-gateway-join architectural patterns during workflow engine refactoring.

Can I use behavioral proofs to test inspector field logic in complex state machines?

Yes, behavioral proofs apply to validating inspector field logic alongside canvas geometry and routing behavior. They enforce product-centric terminology and test coverage for complex state machines requiring diamond-routing behavior.

What is the best way to audit a test suite for transition-first anti-patterns?

The best way to audit for transition-first anti-patterns is running a gateway-focused behavioral proof check. This standardizes workflow editor testing by enforcing a gateway-only authoring model across your entire test suite.