メニュー
Legacy alias for ulw-research. MUST USE when the user asks for ultraresearch, /ultraresearch, or /ultraresearch; immediately load and follow the ulw-research skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ultraresearch |
| description | Legacy alias for ulw-research. MUST USE when the user asks for ultraresearch, /ultraresearch, or /ultraresearch; immediately load and follow the ulw-research skill. |
On Grok Build with lfg installed, translate OpenCode/Codex subagent examples to GrokBuild spawn_subagent calls. Prefer host built-ins when they fit: read-only search → subagent_type: "explore"; catch-all → "general-purpose". Use lfg OMO personas (explorer, librarian, coding, …) only when OMO prompts/models matter. This contract is GrokBuild-only (coding_tool_adapter = grok).
| Intent | GrokBuild tool to use |
|---|---|
| Search/read-only worker | spawn_subagent({ subagent_type: "explore", background: true, description: "...", prompt: "TASK: ..." }) (host built-in; use "explorer" only for OMO persona) |
| Planning worker | spawn_subagent({ subagent_type: "plan", background: true, description: "...", prompt: "TASK: ..." }) |
| Implementation or QA worker | spawn_subagent({ subagent_type: "hephaestus" or "coding", background: true, description: "...", prompt: "TASK: ..." }) |
ultraresearch is the legacy name for ulw-research.
When this skill is selected, immediately load ../ulw-research/SKILL.md and follow it as the source of truth. Treat /ultraresearch, /ultraresearch, and plain ultraresearch exactly like /ulw-research, /ulw-research, and plain ulw-research.
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.
