Menu
Use when GrokBuild needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook (lfg native hook).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | comment-checker |
| description | Use when GrokBuild needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook (lfg native hook). |
lfg registers a Grok PostToolUse hook for successful edit-like tools (write, edit, multi_edit, and equivalents).
When comment-checker reports a warning after a patch, the session receives bounded feedback and should fix or explain the flagged comment before moving on.
Upstream OMO may brand this as a Codex plugin skill. On GrokBuild the same skill is about lfg native PostToolUse feedback, not a Codex-only runtime.
