onboardlisted

# /onboard Guide a repository through Yalla setup and produce a visual onboarding dashboard. The goal is to make the next action obvious: what is already configured, what is missing, and what should not be automated yet. ## Input `$ARGUMENTS` may be empty, a repo path, or a config path. If empty, use the current working directory as the target repo. If it points to `.claude/YALLA.md`, use that file and infer the project root from it. If it points to a directory, use `<directory>/.claude/YALLA.md`. ## Workflow 1. Resolve the target repo and config path. 2. If `.claude/YALLA.md` is missing, explain that Yalla must be installed first and offer the exact `install.sh` command if this is a cloned Yalla repo. 3. Run the onboarding dashboard command when available: ```bash npm run yalla:onboard -- init --config <path-to-target>/.claude/YALLA.md ``` 4. If the command is unavailable because this is a plugin-only install, perform the same checks manually and write `.pipeline/yalla-onboarding-dashboard.html` yourself using the dashboard structure below. 5. Report the dashboard path and the top 3 remaining actions. ## Checks Evaluate these items: - Config exists: `.claude/YALLA.md`. - `base_branch` is set. - `tracking_mode` is set or defaults clearly to `github`. - Commands are configured or intentionally skipped: `test`, `typecheck`, `build`, `lint`. - `test_dir` exists. - `task_system.ready_label`, block labels, and priority labels are configured for GitHub mode. - I