超流
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "hyperflow":https://skillpi.com/zh/skills/deepskill-6af9fea365ac575fcaf241e7fdb1bf9d2df4d69ba17400f5abe76e96dd9e2db6。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/hyperflow/skills/hyperflow/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/hyperflow/skills/hyperflow --skill hyperflow来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 超流 的公开用途。DeepSkill 当前公开目录说明:“在 Codex、Antigravity、Grok 或其他单智能体表面应用 Hyperflow 编排原则时使用。对于非平凡的工程工作(如构建、实现、添加、重构、调试、修复、审查、审计、规划、界定范围、设计、头脑风暴、发布或部署)自动触发。 通过 /hyperflow:hyperflow、"use hyperflow"、"apply the doctrine" 触发,或在任何任务型消息上自动触发。” 适用场景包括搭 Agent 与 AI 应用、写代码与代码审查。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: hyperflow description: | 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. allowed-tools: Read, Write, Edit, Glob, Grep, Agent, Skill, AskUserQuestion, WebSearch, WebFetch, Bash(git:*), Bash(gh:*), Bash(npm:*), Bash(pnpm:*), Bash(npx:*), Bash(python3:*) argument-hint: "[task]" version: 1.0.0 license: MIT compatibility: Portable doctrine — Claude Code, Codex App/CLI, OpenCode, Antigravity, Cursor, Grok tags: [orchestration, doctrine, autonomy, multi-agent, portable] --- # 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 deploy`, `ship with hyperflow` | `deploy` | | `/hyperflow:cache`, `hyperflow cache` | `cache` | | `/hyperflow:status`, `hyperflow status` | `status` | | `/hyperflow:sticky`, `hyperflow sticky` | `sticky` | | `/hyperflow:bridge`, `hyperflow bridge` | `bridge` | | `/hyperflow:flush`, `hyperflow flush` | `flush` | | `/hyperflow:background`, `hyperflow background` | `background` | | `/hyperflow:scaffold`, `hyperflow scaffold` | `scaffold` | Do not answer that `/hyperflow:*` is an unknown command on these surfaces. Strip the alias, load the matching `skills/<name>/SKILL.md`, and follow its workflow. If that workflow says to use unavailable Claude Code tools (`Agent`, `Skill`, or `AskUserQuestion`), emulate them: do worker/reviewer steps inline with visible labels, continue chained skills inline, and use the interaction fallback below when a structured question UI is missing. ## Subagents And Auto-Chain ### Codex When Codex exposes multi-agent tools, map Hyperflow agent dispatches to Codex subagents instead of falling back to inline work: - Hyperflow `Agent` worker/searcher/writer calls map to Codex worker or explorer subagents. - If the callable tool is named `multi_agent_v1.spawn_agent`, use `agent_type: worker` for implementer/writer execution and `agent_type: explorer` for search/codebase-research tasks, then collect results before review. - Spawn independent sibling workers together when the runtime supports parallel subagent calls. - Every agent runs on the current session model — do not switch models per role. Match reasoning effort to task complexity: `low` for trivial docs/config checks, `medium` for normal planning/review, `high` for debugging, architecture, security, or final integration review. - Never request or default to `xhigh`. When Codex does not expose subagent tools in the current session, use the single-agent port above: execute worker/reviewer phases inline with clear labels and continue. ### Grok Grok CLI / Grok Build loads skills from `~/.grok/skills/`, project `.grok/skills/`, and compatible Claude/Cursor skill dirs. Project rules come from `AGENTS.md` / `CLAUDE.md` and `.grok/rules/`. Runtime signal often includes `GROK_AGENT=1`. When Grok exposes `spawn_subagent`, map Hyperflow dispatches as follows: | Hyperflow role | Grok `subagent_type` | |---|---| | implementer / writer / general worker | `general-purpose` | | searcher / codebase research | `explore` | | plan-only research (no file writes) | `plan` | | domain specialists (`architect`, `security-reviewer`, …) | matching type if registered; else `general-purpose` with the specialist charter in the prompt | - Spawn independent sibling workers together when the runtime supports parallel subagent calls. - If subagents are disabled (`GROK_SUBAGENTS=0` or config), run worker/reviewer phases inline with clear labels. - Prefer the native `AskUserQuestion` tool for structural gates when available. - Every agent runs on the current session model — no per-role model selection. - Do not invent Claude Code `Agent` tool calls; use `spawn_subagent` or inline work. ### Auto-chain (all portable hosts) For `/hyperflow:workflow`, use the portable workflow adapter (Codex / OpenCode / Grok branches in the workflow skill) instead of falling back to `scope`: research and planning, `.hyperflow/tasks/` progress tracking when needed, parallel subagents when exposed, inline worker/reviewer phases otherwise, adversarial verification, quality gates, per-task conventional commits, and final synthesis. Do not describe this as native Claude Code dynamic workflow support. These hosts may not expose Claude Code's `Skill` handoff tool. Treat every Hyperflow handoff as an inline auto-chain: - `plan` runs amplify → design → decompose inline, then **stops at its build-location gate** (always asked). It never auto-implements: on "this session" it continues into `dispatch` inline; on "another session" it writes a handoff package; on "stop" it keeps the plan. - `dispatch` offers `audit` and `deploy` structural gates, then runs the selected follow-up inline. - `audit` fix gates continue into `plan` with the generated audit-fix task (which then stops at its own build-location gate). Do not stop with "Skill tool unavailable". Auto-chain is a behavior contract, not a host API requirement. ## Interaction Fallback When a host lacks a structured question UI (or `AskUserQuestion` is unavailable), do not skip the question or silently choose the recommended option. Render the same structural gate as a concise chat block and wait for the user's answer: ```text Hyperflow Question <question> 1. <recommended option> (Recommended) — <short consequence> 2. <option> — <short consequence> ``` Use this fallback for every required clarification or structural gate: Amplify handoff, Spec chain mode, Spec brainstorming questions, Scope ambiguity questions, Dispatch audit/deploy gates, Audit fix gate, Deploy commit-inclusion and push gates, and any security/irreversibility escalation. It is still banned to ask invented confirmation questions such as "should I proceed?". On Grok, prefer the native `AskUserQuestion` tool when present; use the chat-block fallback only if that tool is missing. ## Reasoning Policy - Every agent runs on the current session model — there is no per-role model selection. - Resolve reasoning effort by task/profile: `low` for trivial docs/config checks, `medium` for normal planning/review, and `high` for debugging, architecture, security, and final integration. - Never default portable hosts to exotic max-effort modes (e.g. Codex `xhigh`). ## Core Rules 1. Execute task-shaped requests without confirmation. 2. Clarify only after reading the relevant code and only for genuine ambiguity. 3. Keep long-form plans, specs, task decompositions, and audits under `.hyperflow/`. 4. Use conventional commits, one distinct user task per commit. 5. Never reference the model as the actor in commits, docs, comments, task files, or memory. 6. Respect the security blocklist in `security.md`. ## Workflow Routing | Intent | Workflow | |---|---| | `brainstorm`, `design`, `explore`, "should we" | Research first, ask material questions, then propose approaches | | `scope`, `decompose`, "plan out" | Map affected files, then write a task graph under `.hyperflow/tasks/` | | `big task`, `large migration`, `repo-wide audit`, `run a workflow`, `dynamic workflow` | Use the workflow skill: Claude Code native workflow, or Codex/OpenCode/Grok portable adapter, otherwise decompose through `scope` | | `build`, `implement`, `add`, `refactor` | Decompose, execute batches, self-review, commit per task | | `debug`, `fix it`, "why is X failing" | Root-cause before patching | | `audit`, `review`, "check for issues" | Review findings first, then offer/apply fixes | | `ship`, `push`, `release`, `deploy` | Run gates, commit/release, ask before push | For full multi-agent doctrine, read `DOCTRINE.md` and the linked reference files in this directory.
当前收录版本
1.0.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
跨平台编排原则实现,适用于多种单智能体环境
评分依据
支持多种触发方式:/hyperflow:* 命令、自然语言触发词、自动触发
评分依据
文档结构清晰,包含多个逻辑完整的章节
评分依据
详细说明了在不同宿主环境下的适配策略
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
-
安装或获取外部依赖
使用官方来源并锁定版本,在隔离环境检查安装脚本。当前文档检查不覆盖后续下载的代码。
主文档提及 · 第 6 行
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。