hyperflow-cache
Hyperflow memory manager. Use to view, search, add, edit, prune, or clear hyperflow project memory — "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y". CRUD over .hyperflow/memory/ only — never touches source code.
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.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
hyperflow-cache — memory CRUD (Antigravity single-agent)
Manage .hyperflow/memory/ entries. Only memory files — never source code. Follow the hyperflow doctrine.
Operations
- view / list — print the entries in
.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md. - search
- add — append a tagged entry to the right category file (decisions / learnings / pitfalls / patterns). Use the format:
##then-.(recorded ) - edit
- prune / clear — remove stale or wrong entries. Confirm via AskUserQuestion before a destructive clear (binary Yes/No).
Rules
- Scope is
.hyperflow/memory/only. Don't record what the repo/git already captures; record the non-obvious why.