askill
orchestration

orchestrationSafety 90Repository

Orchestrate UX design work across research, architecture, interaction, visual, and strategy competencies. Entry point for UX projects spanning multiple areas. Routes to specialized skills based on task requirements. Use for: UX design, user experience, UX project, design process, UX workflow, full UX cycle, end-to-end UX, UX competencies, which UX skill, UX help, coordinate UX disciplines, UX team handoffs.

0 stars
1.2k downloads
Updated 1/27/2026

Package Files

Loading files...
SKILL.md

UX Orchestration

Orchestration skill for comprehensive UX work spanning research, architecture, interaction, visual design, and strategy.

When to Use

  • Starting a new UX project that spans multiple competencies
  • Unsure which specialized UX skill to invoke
  • Need to coordinate work across UX disciplines
  • Planning UX team workflow or handoffs

When NOT to Use

  • Task is clearly within one competency (use sub-skill directly)
  • Pure implementation work (coding, deployment)
  • Non-design tasks

Sub-Skills

SkillInvoke WhenKey Deliverables
researchUnderstanding users, testing designsPersonas, journey maps, usability reports
architectureOrganizing content, navigationSitemaps, taxonomies, navigation specs
interactionDesigning flows, behaviorsWireframes, prototypes, user flows
visualCreating UI, design systemsComponents, style guides, design tokens
strategyAligning UX with businessRoadmaps, metrics, maturity assessments

Quick Decision Guide

What do you need to do?
|
+---> Understand users or test designs?
|     +---> Use: research
|
+---> Organize content or navigation?
|     +---> Use: architecture
|
+---> Design flows or prototypes?
|     +---> Use: interaction
|
+---> Create visual UI or design system?
|     +---> Use: visual
|
+---> Align UX with business goals?
|     +---> Use: strategy
|
+---> Multiple areas or unsure?
      +---> Continue reading this skill

The UX Process (Double Diamond)

flowchart LR
    subgraph Discover["Discover"]
        D1[Research Users]
        D2[Understand Context]
        D3[Identify Problems]
    end

    subgraph Define["Define"]
        Df1[Synthesize Insights]
        Df2[Define Problems]
        Df3[Set Strategy]
    end

    subgraph Develop["Develop"]
        Dv1[Ideate Solutions]
        Dv2[Create Prototypes]
        Dv3[Test & Iterate]
    end

    subgraph Deliver["Deliver"]
        Dl1[Refine Design]
        Dl2[Specify Details]
        Dl3[Hand Off]
    end

    Discover --> Define --> Develop --> Deliver

    style Discover fill:#e3f2fd
    style Define fill:#fff3e0
    style Develop fill:#e8f5e9
    style Deliver fill:#fce4ec

Competency Mapping by Phase

PhasePrimary SkillSupporting Skills
Discoverresearchstrategy
Definearchitectureresearch, strategy
Developinteractionvisual, research
Delivervisualinteraction

Orchestration Patterns

Pattern 1: Sequential (Traditional)

Research --> IA --> IxD --> Visual --> Handoff

Best for: Well-defined projects, waterfall environments

Pattern 2: Parallel Tracks

Research ---------------------------->
         +-- IA --------------------->
         +-- IxD -------------------->
         +-- Visual ----------------->
Strategy ---------------------------->

Best for: Agile sprints, time-constrained projects

Pattern 3: Iterative Loops

Research <--> Define <--> Design <--> Test

Best for: High-uncertainty projects, continuous discovery


Agent Coordination for UX Projects

When using multiple agents for parallel UX work:

Handoff Checkpoints

FromToCheckpoint Artifacts
researcharchitecturePersonas, mental models, card sort data
researchinteractionUser flows, task analysis, pain points
architectureinteractionSitemap, taxonomy, navigation spec
interactionvisualWireframes, component list, interaction specs
strategyAllOKRs, success metrics, constraints

Parallel Execution Rules

  1. strategy can run parallel to all others (provides constraints)
  2. research must complete Discovery before Define
  3. architecture and interaction can run parallel after IA basics
  4. visual needs wireframes before full component design

Full Project Procedure

Step 1: Project Scoping

  • Define project goals and constraints
  • Identify stakeholders
  • Determine timeline and resources
  • Invoke: strategy for roadmap and metrics

Step 2: Discovery Research

  • Conduct user interviews
  • Analyze existing data
  • Create personas and journey maps
  • Invoke: research

Step 3: Define Structure

  • Create information architecture
  • Design navigation patterns
  • Validate with card sorting
  • Invoke: architecture

Step 4: Design Interactions

  • Map user flows
  • Create wireframes
  • Build prototypes
  • Invoke: interaction

Step 5: Apply Visual Design

  • Establish design tokens
  • Create component library
  • Apply visual styling
  • Invoke: visual

Step 6: Validate & Iterate

  • Conduct usability testing
  • Measure against metrics
  • Iterate based on findings
  • Invoke: research for testing

Definition of Done (Full UX Project)

  • User research insights documented
  • Information architecture validated
  • Interaction flows complete and tested
  • Visual design system established
  • Success metrics defined and baseline captured
  • Handoff documentation complete

Guardrails

Always:

  • Start with understanding users (even briefly)
  • Define success metrics before designing
  • Test designs with real users
  • Document decisions and rationale

Never:

  • Skip research entirely
  • Design in isolation from business goals
  • Ignore accessibility requirements
  • Assume without validating

Reference Files

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

96/100Analyzed 2/11/2026

An exceptionally well-structured orchestration skill that serves as a master controller for UX workflows. It features clear decision logic, process mapping, and coordination rules.

90
100
85
95
98

Metadata

Licenseunknown
Version-
Updated1/27/2026
Publisherteslasoft-de

Tags

ci-cdgithub-actionsobservabilitytesting