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.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add jeremylongshore/tons-of-skills-marketplace --skill hyperflow-status --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Hyperflow Status?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-hyperflow-status)More formats (shields.io, HTML) on the badges page.
---
name: hyperflow-status
description: 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.
---
# 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
1. Read `.hyperflow/tasks/*.md`; for each, report the status block (progress bar, sub-tasks done/total, branch).
2. Count `.hyperflow/specs/*.md` and `.hyperflow/audits/*.md`.
3. Count `.hyperflow/memory/*` entries.
4. Print a compact summary: active tasks + their progress, spec/audit counts, memory size. If `.hyperflow/` is absent, say so and suggest `hyperflow-scaffold`.
## Rules
- Never modify any file. Never dispatch work. Output is a single status block.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...