USING UXDLAvailable

Work with Slices

A Screen describes part of the product model; a Slice describes the exact bounded scope you are discussing.

Slice vs Screen Distinction

Screens and States form the permanent interaction graph of your product. Slices define a temporary or bounded scope (such as a Jira story, user journey, sprint task, or bug fix) mapped across existing screens.

Mapping Acceptance Criteria

Rendering diagram...

A Slice references stable screen, state, action, and relation addresses.

Complete Slice YAML Spec

YAML

1slices:
2  cancellation_flow:
3    name: Self-Serve Cancellation & Retention Journey
4    type: story
5    actor: customer
6    screens:
7      - billing
8      - cancellation_review
9    acceptance:
10      - Workspace owner can trigger cancel_subscription from billing.
11      - System presents cancellation_review modal with retention offer.
12      - Finalizing cancellation sets billing state to cancelled.
13      - Accepting retention offer returns user to billing in active state.