team-ui

Coordinating a UI design pipeline involves orchestrating phase transitions and assigning subagents for ux-design, implementation, review, and QA. This skill manages the full workflow, delegating tasks to specialists like ui-programmers and art-directors while enforcing write protocols.

Yes, you can use a team workflow for game UI and product admin interfaces. The system supports domain routing for game and product contexts, applying the same UX pipeline coordination to different interface types with decision-points at each phase.

Subagents handle UI implementation and accessibility reviews by executing delegated responsibilities within their specialties. The workflow assigns an engine UI specialist for implementation and an accessibility-specialist for reviews, gathering input and selections before enforcing explicit user approvals for writes.

The best way to manage design handoffs and QA evidence in a UX pipeline is to route all UI work through a prescribed sequence of phases. A qa-tester subagent collects evidence during the final stages, ensuring implementation matches the original UX spec before final approval.

Yes, you need explicit user approvals for writes during UI team collaboration. The pipeline enforces strict write protocols, requiring user input at decision-points before any changes are committed, ensuring all subagent work aligns with project standards.