hyperflow-dispatch
Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire up", "run the plan", "execute the task". Works batches sequentially with self-review and per-task commits. In Antigravity there is no sub-agent fan-out — the single agent does each batch itself.
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-dispatch --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# hyperflow-dispatch — execution phase (Antigravity single-agent) Execute the task file from `hyperflow-plan`. **No sub-agent dispatch and no model tiers in Antigravity** — you do each batch yourself, then self-review before committing. Follow the `hyperflow` doctrine. ## Per batch 1. **Implement** every sub-task in the batch (sequentially; they were planned as small, independent units). 2. **Self
What does the hyperflow-dispatch skill do?
Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire up", "run the plan", "execute the task". Works batches sequentially with self-review and per-task commits. In Antigravity there is no sub-agent fan-out — the single agent does each batch itself.
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-dispatch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.