Menú
Use when the user asks about lfg/GrokBuild rules injection, project rules files, matching, or environment configuration.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 | rules |
| description | Use when the user asks about lfg/GrokBuild rules injection, project rules files, matching, or environment configuration. |
Rules injection is automatic once the lfg Grok plugin is enabled. It injects:
SessionStart and UserPromptSubmit (native rules hook + config loader)Dynamic PostToolUse output is injected as additional context when the host attaches hook output. If hook context is not visible, read matching rule files from disk directly.
Supported project sources:
CONTEXT.md.omo/rules/**/*.md.claude/rules/**/*.md.cursor/rules/**/*.md.github/instructions/**/*.md.github/copilot-instructions.mdAGENTS.md (fail-closed project awareness)Prefer lfg/Grok-owned knobs when present. Codex-only CODEX_RULES_* names may appear in upstream OMO docs as historical reference; on GrokBuild do not require CODEX_HOME or Codex plugin layout.
Upstream may brand this as "Codex Rules". On GrokBuild the owner is lfg native rules (lfg-native-rules.mjs + src/core/omo/rules-engine).