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.
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-status --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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/memor
What does the hyperflow-status skill do?
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.
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-status --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.