hyperflow-scaffold

Hyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — "init hyperflow", "set up hyperflow", "refresh hyperflow", "scaffold hyperflow". One-shot setup of the .hyperflow/ project cache + memory and the .agent/workflows/hyperflow* slash commands. Does not start the spec → scope → dispatch chain.

hyperflow Plugin
ai agency Category

Allowed Tools

No tools specified

Provided by Plugin

hyperflow

Fifteen specialized slash commands turn one Claude session into a structured multi-agent engineering pipeline. Thinking models orchestrate, triage, and review; worker models execute in parallel — every step is a Worker → Reviewer pair, and every non-trivial phase fans into sub-phases with their own reviewers. Auto-routing is on by default — say 'audit the diff', 'debug this test', 'large migration', or 'run a workflow' and the orchestrator routes to the right skill without the /hyperflow:* prefix. /hyperflow:workflow uses Claude Code dynamic workflows for big tasks and a portable Codex/OpenCode adapter where native workflows are unavailable; /hyperflow:spec asks the questions a senior engineer would; /hyperflow:scope decomposes into a batched task graph; /hyperflow:dispatch fans out persona-stitched workers under tiered review; /hyperflow:amplify rewrites a rough prompt into a high-quality one before you run it. 15 composable personas, 6 adaptive flow profiles, and persistent project memory compound across sessions. Works across Codex App/CLI, Claude Code, OpenCode, and Antigravity.

ai agency v4.26.1
View Plugin

Installation

This skill is included in the hyperflow plugin:

/plugin install hyperflow@claude-code-plugins-plus

Click to copy

Instructions

hyperflow-scaffold — project setup (Antigravity single-agent)

One-shot setup of hyperflow's project surfaces. Follow the hyperflow doctrine.

Steps

  1. Create the .hyperflow/ cache at the repo root if absent:
  • .hyperflow/memory/ with decisions.md, learnings.md, pitfalls.md, patterns.md (empty stubs, each with a one-line header).
  • .hyperflow/tasks/, .hyperflow/specs/, .hyperflow/audits/ (empty dirs).
  1. Write context files (.hyperflow/profile.md, architecture.md, conventions.md) by reading the repo: stack, top-level layout, test/lint conventions, commit conventions. Keep each short and factual.
  2. Install project slash commands: copy the seven hyperflow* workflow files into /.agent/workflows/ (so /hyperflow, /hyperflow-spec, … resolve in Antigravity's / menu). Source: the templates/antigravity/workflows/ shipped with hyperflow.
  3. Note that global hyperflow skills live in ~/.gemini/config/skills/ (auto-trigger) and global rules in ~/.gemini/AGENTS.md.
  4. Print a one-line summary of what was created. Do NOT start the chain.

Rules

  • Idempotent — never clobber existing .hyperflow/ content; only create what's missing.
  • .hyperflow/tasks and .hyperflow/specs are runtime artefacts; .hyperflow/memory is durable and worth committing.

Ready to use hyperflow?