hyperflow

# Hyperflow Doctrine (single-agent port) Apply Hyperflow's behavioral floor in surfaces that load skills but do not provide the full Claude Code multi-agent runtime. ## Runtime Adaptation Codex, OpenCode, Antigravity, and Grok often run one foreground agent (or a host-specific subagent API). Where the full doctrine says to dispatch parallel workers under reviewers: - Prefer the host's subagent API when it exists (Codex spawn, OpenCode Task, Grok `spawn_subagent`). - Otherwise do the work yourself, one coherent batch at a time. - Self-review each batch before moving on. - Run a final integration self-review over the cumulative diff. - Preserve the same autonomy, clarification, commit cadence, file-first artefact, no-attribution, and security rules. ## Portable Function Router (Codex / OpenCode / Grok) These hosts load Hyperflow as skills, not as native Claude-style slash commands. Treat these user messages as function aliases and execute the matching skill workflow inline in the current thread: | User says | Run | |---|---| | `/hyperflow:plan`, `hyperflow plan`, `design with hyperflow`, `decompose with hyperflow` | `plan` | | `/hyperflow:dispatch`, `hyperflow dispatch`, `run the hyperflow plan` | `dispatch` | | `/hyperflow:workflow`, `hyperflow workflow`, `run a workflow` | `workflow` | | `/hyperflow:trace`, `hyperflow trace`, `debug with hyperflow` | `trace` | | `/hyperflow:audit`, `hyperflow audit`, `review with hyperflow` | `audit` | | `/hyperflow:deploy`, `hyperflow...