dev-dashboard-tui

## Launch the Dev Dashboard TUI The dev-dashboard TUI is the terminal-native sibling of the web `/dev-dashboard`: the same cross-project `.dev/` feature portfolio — a recency-sorted project rail, per-feature status and progress, and a detail pane — rendered natively in the terminal for SSH/tmux/no-browser workflows. It live-refreshes as `.dev/` PRDs change. ### Why the agent cannot start it A TUI is a **foreground, interactive** process that must own a real terminal (TTY). Claude Code's `Bash` tool runs commands against a detached, non-interactive pipe — an Ink app rendered there produces garbage and never receives keystrokes. Unlike `/dev-dashboard` (which backgrounds an HTTP server and reports a URL), this skill **hands the launch command to the user** to run in their own terminal. **Do not attempt to spawn the TUI from a `Bash` tool call.** ### Step 1: Resolve the launch command The launcher lives at `scripts/launch.sh` within this skill's directory. Build the absolute path to it (call it `$LAUNCH`). Optionally confirm the bundled artifact is present first: ```bash test -f "$LAUNCH" && echo ok ``` Where `$LAUNCH` is the absolute path to `scripts/launch.sh` within this skill's directory. Use `$HOME` instead of literal home paths. ### Step 2: Tell the user to run it Present the exact command for the user to paste into their **own** terminal (with `$LAUNCH` resolved to the real absolute path): ``` bash "<absolute path>/scripts/launch.sh" ``` To scan a specific dir...