workflow-stage-runtime-projection

Map workflow stage definitions into Prism runtime states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the friction between high-level workflow design and low-level runtime implementation by allowing authors to define service stages once and projecting them into Prism-compatible shells without manual metadata duplication.

Core Features & Use Cases

  • Stage-Centric Authoring: Define intent, actors, and deadlines at the stage level rather than managing individual state transitions.
  • Audience Projections: Automatically map authored views to specific audiences like public, member, or operator roles.
  • Runtime Compatibility: Ensures that high-level stage definitions remain compatible with Prism's core requirements like state versions, response envelopes, and transition keys.

Quick Start

Use the workflow-stage-runtime-projection skill to map your current stage-based workflow definition into a Prism-compatible runtime shell.

Frequently Asked Questions about workflow-stage-runtime-projection

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

FAQPage Schema
How do I map high-level workflow stages into Prism runtime states without duplicating metadata?

Workflow stage projection translates high-level service stages into low-level Prism runtime states automatically. It allows authors to define intent, actors, and deadlines at the stage level rather than managing individual state transitions manually.

Can I generate audience-specific projections for public, member, or operator roles in a state machine?

Audience projections automatically map authored workflow views to specific audiences like public, member, or operator roles. This allows you to maintain a single stage-centric workflow definition while serving tailored state views to different user types.

How do I ensure structural integrity of workflow response envelopes and state metadata during projection?

Structural integrity of workflow response envelopes is maintained by ensuring high-level stage definitions remain compatible with Prism's core requirements. The projection process automatically validates state versions, response envelopes, and transition keys.

What is the best way to author workflow transitions for complex service blueprints?

The best way to author complex service blueprints is stage-centric authoring, defining intent, actors, and deadlines at the stage level. This approach facilitates component-driven transitions without manually managing individual state changes.

Does this workflow projection approach work with Umbraco and Prism state machines?

Workflow stage projection works with Prism state machines by mapping definitions into compatible runtime shells. It is designed for environments using service design and state machine principles, ensuring compatibility with Prism's transition keys and state versions.