hyper-researchlisted

# hyper-research Pre-implementation research gate. By default runs **both** the Codex research path and the Claude research path in parallel, producing two artifacts (`.hyperclaude/research/<timestamp>-<slug>.md` from Codex and `.hyperclaude/research/<timestamp>-<slug>-claude.md` from Claude) that share one frontmatter `slug:`; you read them and integrate findings into your next planning step. A single path runs only on explicit user request. ## When to use - User typed `/hyperclaude:hyper-research <task>`. - You're about to start substantial new work and want a parallel Codex + Claude research context dump. Skip when: - The task is a small fix or rename. - A recent research file (within ~30 min) already covers this task. ## How to invoke `--resume` is not supported (deferred — research is not iterative). **Invocation argument:** $ARGUMENTS ### Path selection Two research paths exist (Codex and Claude). Pick by reading the user's intent — this is a plain-language rule, **not** a flag/token/`$ARGUMENTS` grammar: - **Default** (a normal `/hyperclaude:hyper-research <task>`, or any case not explicitly single-path) → **both paths in parallel** (Codex + Claude), producing two artifacts that share one slug. - ONLY if the user EXPLICITLY asks for **Codex only / no Claude** → **Codex path** alone. - ONLY if the user EXPLICITLY asks for **Claude only / Claude-native / no-Codex / a Claude second opinion** → **Claude path** alone. - If the intent is genuinely unclear → treat i