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 plan → dispatch chain.

Allowed Tools

No tools specified

Provided by Plugin

hyperflow

Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.

ai agency v5.9.0
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 hyperflow* workflow files into /.agent/workflows/ (so /hyperflow, /hyperflow-plan, /hyperflow-design, … 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?