grokodex-critiquelisted

# Grokodex Critique Read-only design challenge through Grokodex MCP. **Does not modify the repo.** Focuses on approach, tradeoffs, and failure modes — not a line-by-line defect hunt. ## When to use - User asks to challenge the design, critique the approach, or "挑刺方案 / 有没有更好的做法" - Tradeoffs, alternatives, risks, and failure modes — no implementation - Not for defect-focused code review → `grokodex-review` - Not for apply fixes → `grokodex-run` ## Tool preference 1. Always call MCP `grok_run` with **`profile: "critique"`** (required). 2. Forbidden: shell/`grok` for the critique task. 3. Do not call `grok_run` without `profile` for a pure critique request. ## Steps 1. Determine scope: working tree (default) or user-specified base ref. 2. Collect with host tools: `git status`, staged/unstaged diff, or `git diff base...HEAD`. For large diffs, summarize and include the most critical file hunks / design-relevant context. 3. If there is nothing to critique, tell the user and **stop** (do not call MCP). 4. Build `prompt` including: scope label, collected diff/context, critique axes (approach correctness, alternatives, risks, failure modes, maintainability at design level). 5. Call: ```text grok_run prompt: <assembled> profile: critique # optional: cwd, model, host_thread_id, max_turns, timeout_ms ``` 6. Present `text` findings. **Do not** start editing in the same turn unless the user explicitly asks to fix — then switch to `grokodex-run` **without** profile. ## Permis