golisted

> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Entry point for the qq development workflow. Detects your current state and guides you to the right skill. This skill is a **controller**, not an implementation engine. It should read real project state first and only fall back to prompt/context heuristics when the state is ambiguous. ## Hard Rules - If `qq-project-state.py` is available, you **must** run it before inspecting git history, branch divergence, commit counts, or repo-wide document context. - If `qq-project-state.py` returns valid JSON, treat it as the primary source of truth. - When project state is available, do **not** summarize branch size, recent commits, or unrelated repo-wide artifacts unless the user explicitly asked for that analysis. - Keep the answer short and action-oriented: - current `work_mode` - current `policy_profile` - current `recommended_next` - one-sentence why - Do not turn `/qq:go` into a repo audit. It is a router. - Do NOT explain the pipeline order (design → plan → execute). The user already knows. Just recommend the next step and ask to proceed. Arguments: $ARGUMENTS - A file path (design doc, plan, or code file) - A brief description of what to build - `--auto`: mode-aware automati