القائمة
Use when GrokBuild needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace (lfg MCP lsp surface).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
MUST USE for planning before coding: 5+ steps, ambiguous scope, multiple modules, architecture decisions, a vague 'just make it good / figure out what to build' brief, or any request to plan, interview, or break work down. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode, just make it good, figure out what to build.
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
Persistent code-mode kernels (JS/Python) for incremental computation — omp/senpi eval analog on GrokBuild via lfg MCP. Use when multi-step code execution, data exploration, or stateful REPL beats one-shot bash.
| name | lsp |
| description | Use when GrokBuild needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace (lfg MCP lsp surface). |
Call lsp MCP tools through the tool interface; lsp.* / mcp__lsp__* are tool-call names, not shell commands.
On GrokBuild with lfg, the local MCP runtime exposes language-service helpers (for example typescript_diagnostics). Prefer those tools over inventing shell LSP wrappers.
lsp.status: list configured, installed, missing, disabled, and active language servers (when available).lsp.diagnostics / TypeScript diagnostics: check one file or directory for diagnostics. Prefer severity error after edits.lsp.goto_definition: locate a symbol definition from file, line, and character (when available).lsp.find_references: find usages of a symbol across the workspace (when available).lsp.symbols: inspect document symbols or search workspace symbols (when available).lsp.prepare_rename / lsp.rename: rename safety (when available).~/.codex/lsp-client.json is not the GrokBuild owner path; do not require Codex home for Grok sessions.Use status/diagnostics first when tools report a missing language server.
Upstream OMO/Codex docs may mention .codex/lsp-client.json. On GrokBuild, treat that as historical reference only; use lfg MCP + project LSP tooling.