team-tui

Automated TUI testing in a team pipeline is handled by intercepting the verify stage to spawn parallel test workers. These workers run component, hook, and integration tests to validate TUI changes before completion, outputting results under the TUI test directory for review.

Interactive E2E tests for CLI components are supported using tmux when the --interactive flag is requested. The workflow includes prerequisites validation and test pattern guidance to ensure the interactive testing environment is correctly configured before execution.

The /team skill is required to coordinate TUI QA orchestration because this workflow extends it by preserving base plan, prd, and exec stages. It intercepts the verify stage to inject parallel TUI test workers while relying on the parent skill for overall pipeline management.

Parallel TUI test automation auto-detects changed TUI files and assigns scoped QA tasks to dedicated workers. By targeting only modified areas, it maximizes test coverage without slowing down unchanged components, hooks, or integration paths during the verify stage.

The best way to structure TUI test scopes is using the provided categories of components, hooks, and integration. This scope categorization allows the parallel test workers to target specific TUI layers independently, ensuring comprehensive validation across the CLI interface architecture.

You should avoid parallel TUI test workers if your project does not use the /team workflow orchestration or lacks TUI components under packages/cli/src/tui. The skill is specifically designed to intercept team pipeline verify stages and requires that structural context to function correctly.