Menu

Individual skill

hyperflow

0upvotes

Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, scope, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, "use hyperflow", "apply the doctrine", or automatically on any task-shaped message.

plugins/ai-agency/hyperflow/skills/hyperflow/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top