hyperflow-status
Hyperflow project status. Use to see current hyperflow state — "what is hyperflow doing", "show task progress", "where are we". Read-only — reports in-flight tasks, memory count, and progress. Never modifies state or runs work.
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.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
hyperflow-status — read-only state (Antigravity single-agent)
One-screen view of hyperflow project state. Read-only — never edits files or runs work. Follow the hyperflow doctrine.
Steps
- Read
.hyperflow/tasks/*.md; for each, report the status block (progress bar, sub-tasks done/total, branch). - Count
.hyperflow/specs/.mdand.hyperflow/audits/.md. - Count
.hyperflow/memory/*entries. - Print a compact summary: active tasks + their progress, spec/audit counts, memory size. If
.hyperflow/is absent, say so and suggesthyperflow-scaffold.
Rules
- Never modify any file. Never dispatch work. Output is a single status block.