skills.rest
ThorStarlord
ThorStarlordCOMMUNITY
Explore all skills by this author →
GitHub

ui-orchestrator

Read project state and recommend the next required UI specification skill.

1|Updated May 6, 2026
Search Tags:#agent handoff#interface contracts#documentation discovery#ui orchestration#spec routing#status-driven workflow
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-orchestrator-thorstarlord
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-orchestrator
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/ui-orchestrator
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-orchestrator-thorstarlord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interface Skills prevents UI-spec drift by guiding you to the single next missing or unapproved step in a Spec Package instead of letting an AI or agent guess what to do next.

Core Features & Use Cases

  • Pipeline-aware routing: Scans spec package files in order and recommends the earliest gap based on status values like draft vs approved.
  • Context re-establishment: Helps when a project is handed off to a new session/model by re-reading what exists and what’s incomplete.
  • Spec-recovery scoping: Recommends ui-surface-inventory first when broader recovery is needed, to avoid an unmanageable all-at-once recovery.

Quick Start

Use ui-orchestrator when you ask what to do next in your UI Spec Package so it recommends exactly one next skill based on which spec files are missing or still in draft.

Frequently Asked Questions about ui-orchestrator

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

FAQPage Schema
How do I determine the next step in a UI specification workflow?▼

To determine the next step in a UI specification workflow, the system scans your working directory for the spec package manifest. It checks file completeness and approval status to output exactly one routing decision for the next required action.

What is status-driven workflow routing for interface contracts?▼

Status-driven workflow routing for interface contracts is a mechanism that checks artifact status values like draft versus approved. It identifies the earliest missing or unapproved file in a pipeline to prevent UI spec drift during agent handoffs.

How do I resume a UI spec pipeline after an agent handoff?▼

To resume a UI spec pipeline after an agent handoff, re-establish context by re-reading existing project state files. The system treats any draft artifact as a gap and recommends the single next required specification skill to continue.

When do I need spec-recovery scoping for UI documentation discovery?▼

You need spec-recovery scoping for UI documentation discovery when broader recovery is required after a major pipeline disruption. It targets surface inventory first to prevent an unmanageable all-at-once recovery of your interface contracts.

Does the UI spec routing process perform design work?▼

The UI spec routing process does not perform design work. It strictly outputs routing decisions by scanning the working directory for the spec package manifest and checking pipeline file completeness and approval status.

Related Skills

Explore More Design & Creative Skills→
ApothecaryManApothecaryMan

speckit-tasks

Generate a dependency-ordered tasks.md file from spec-kit design artifacts.

Community
Advanced
lhpaullhpaul
9

workflow-spec-reviewer

Review workflow specifications for gaps against the repository's spec review protocol.

Community
Intermediate
ThorStarlordThorStarlord
1

ui-surface-inventory

Classify product UI scopes into App Shell, Journey, Route, and Sub-surface.

Community
Intermediate
heymishyheymishy

coverage-map

Read test plans and pipeline-state.json to report per-story and per-AC coverage status.

Community
Intermediate