메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, OpenCode, or another portable surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, "use hyperflow", "apply the doctrine", or automatically on any task-shaped message.
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
Use when the user wants to archive completed hyperflow artefacts for a slug, clear ephemeral leftovers (usage ledgers, session log bloat, settled commit queues, terminal background buffers), and optimise durable memory — never source code. Also the phase contract lifecycle skills (dispatch/deploy/handoff) invoke at completion when cleanup.reapOnComplete is true. Trigger with /hyperflow:reap, hyperflow reap, "reap completed tasks", "archive finished slug", "clean up after dispatch", "post-completion cleanup".
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it", "run the batches".
Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list handoffs", "pick up the handoff", "review the handoff build".
| name | hyperflow-cache |
| description | 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. |
Manage .hyperflow/memory/ entries. Only memory files — never source code. Follow the hyperflow doctrine.
.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md.<term> — grep the memory files; show matching entries with their file + heading.## <topic> then - <fact> (recorded <YYYY-MM-DD>).<entry> — update an existing entry in place (don't duplicate)..hyperflow/memory/ only. Don't record what the repo/git already captures; record the non-obvious why.