
Status
FreeGet a live overview of your hyperflow project state.
Free · Opens the source repo
What Status does
The Status skill provides a read-only snapshot of your current hyperflow project, allowing you to quickly assess the project's state without modifying any data. It is designed for developers and designers who need to monitor ongoing tasks and overall project health at a glance. By using the command /hyperflow:status, users can access vital information about the project's version, profile freshness, memory count, and detailed progress on all active tasks.
The skill is divided into two main sections. The first is a static snapshot that includes the version of the project, the freshness of the profile based on its last modification time, and the current memory count derived from the project's memory index. The second section focuses on in-flight work, providing live progress updates for each active task. This includes details such as the number of completed sub-tasks, running tasks, and pending tasks, along with a visual progress bar to indicate how much work has been done versus how much remains.
This skill is particularly useful for teams working on complex projects where multiple tasks are handled simultaneously. By having a centralized view of the project state, team members can make informed decisions about resource allocation and task prioritization. The read-only nature of the skill ensures that users can monitor progress without the risk of inadvertently modifying the project state, making it a safe tool for oversight.
Overall, the Status skill is an essential tool for anyone involved in managing hyperflow projects, providing clarity and insight into ongoing work without the need for extensive navigation through project files.
When to use it
Use this skill when you need to quickly check the status of your hyperflow project and monitor live task progress.
When not to use it
This skill is not suitable for modifying project states or for use in automated workflows, as it is strictly read-only.
What you can build with it
Quick Project Health Check
Use the Status skill to get an immediate overview of your project's state during team meetings or check-ins.
Monitor Task Progress
Keep track of ongoing tasks and their progress without needing to dive into individual task files.
Assess Project Version and Freshness
Quickly verify the version of your hyperflow project and the freshness of the profile to ensure you're working with the latest data.
How to install Status
View source1. Install with the skills CLI
npx skills add jeremylongshore/claude-code-plugins-plus-skills/status --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by jeremylongshoreStatus
Read-only snapshot of the current hyperflow project, with live progress on every active task file. Standalone — does not auto-chain and is never invoked by other skills. Invoked manually via /hyperflow:status.
The skill has two sections:
- Static snapshot — version, profile freshness, memory count
- In-flight work — per-task live progress (sub-tasks done/total, tokens, wall-clock, ETA)
What to read
Static snapshot
| Field | Source | Fallback |
|---|---|---|
| Version | Latest git tag matching v* + tag commit date | (missing) |
| Profile | .hyperflow/profile.md file modification time | (missing) |
| Memory | Line count of .hyperflow/memory/index.md minus header rows | (none) |
| Active tasks | Files matching .hyperflow/tasks/*.md | (none) |
| Active features | Folders matching .hyperflow/features/*/feature.md | (none) |
Active features (multi-phase work)
For every .hyperflow/features/*/feature.md (see feature-phases.md), parse its
## Status block and the phase roster, then for each phase-<n>-*/phase.md show the phase status + Progress bar:
── Feature: checkout-redesign ── (2 / 3 phases)
✓ phase-1-data-layer completed
▸ phase-2-api in_progress ████░░░░ 2/5 tasks · running: T3-handlers
phase-3-ui pending depends on phase-2
The per-phase bar uses the same parsing as the per-task-file section below (each phase.md carries the same
## Status block shape). Omit this section when no .hyperflow/features/*/ exist.
In-flight work (per task file)
For every .hyperflow/tasks/*.md, parse its ## Status block (written by /hyperflow:plan at creation and updated by /hyperflow:dispatch after each sub-task PASS — see plan/SKILL.md Step 10):
| Field | Source | Behaviour |
|---|---|---|
| Slug | basename of the task file minus .md | always present |
| Done / total | Sub-tasks: <done> / <total> from Status block | falls back to counting [x] vs [x]+[ ] checkboxes if Status missing |
| Done sub-task names | lines with [x] from the ## Batches section | listed under the bar |
| Running sub-task | the first [~] checkbox (dispatch marks ~ while a sub-task is mid-flight) | (idle) if none |
| Pending sub-task count | count of [ ] checkboxes | shown as N pending |
| Tokens used | Tokens used: line from Status block | (not tracked yet) if Status absent |
| Wall-clock | Wall-clock: line from Status block | (not started) if no Started: |
| ETA | ETA: line from Status block | (computing) if <3 sub-tasks done |
How to compute each field
Version
tag=$(git tag --sort=-v:refname | grep -E '^v[0-9]' | head -1)
released=$(git log -1 --format=%ci "$tag" 2>/dev/null | cut -d' ' -f1)
If $tag is empty → print (missing).
Profile freshness
profile=".hyperflow/profile.md"
now=$(date +%s)
mtime=$(stat -f %m "$profile" 2>/dev/null || stat -c %Y "$profile" 2>/dev/null)
hours=$(( (now - mtime) / 3600 ))
- File absent →
(missing) hours <= 24→fresh (analyzed Xh ago)hours > 24→stale (analyzed Xh ago)
Memory entry count
Count table-body rows in .hyperflow/memory/index.md (lines starting with |, minus header + separator):
count=$(grep -c '^|' .hyperflow/memory/index.md 2>/dev/null)
entries=$(( count - 2 ))
If file absent or count ≤ 0 → (none).
Active tasks list
tasks=$(ls .hyperflow/tasks/*.md 2>/dev/null)
If no files → show (none) and skip the In-flight section entirely.
Per-task Status parsing
For each .hyperflow/tasks/<slug>.md:
# Extract Status block fields
sub_done=$(grep '^Sub-tasks:' "$file" | sed -E 's|.*: *([0-9]+) */ *([0-9]+).*|\1|')
sub_total=$(grep '^Sub-tasks:' "$file" | sed -E 's|.*: *([0-9]+) */ *([0-9]+).*|\2|')
tokens=$(grep '^Tokens used:' "$file" | sed 's|^Tokens used: *||')
wall=$(grep '^Wall-clock:' "$file" | sed 's|^Wall-clock: *||')
eta=$(grep '^ETA:' "$file" | sed 's|^ETA: *||')
started=$(grep '^Started:' "$file" | sed 's|^Started: *||')
If the Status block is missing or malformed (old-style task file from before this format), fall back to counting checkboxes directly:
done=$(grep -c '^- \[x\]' "$file" 2>/dev/null)
running=$(grep -c '^- \[~\]' "$file" 2>/dev/null)
pending=$(grep -c '^- \[ \]' "$file" 2>/dev/null)
total=$(( done + running + pending ))
Done sub-task names (for the indented list)
grep '^- \[x\]' "$file" | sed -E 's|^- \[x\] *||' | head -5
Show up to the last 3 completed + the currently running sub-task. If there are more than 3 done, prefix the list with … (N earlier done).
Running sub-task
The dispatch skill marks the in-flight sub-task with [~] while the worker is running. After PASS + commit, dispatch flips [~] → [x].
running=$(grep '^- \[~\]' "$file" | sed -E 's|^- \[~\] *||' | head -1)
If no [~] line exists → the dispatch is either between sub-tasks (idle for milliseconds) or has handed control back. Show (idle — last update Xm Ys ago) based on Last update: timestamp.
Progress bar
20-char ASCII bar based on done / total:
[████████████░░░░░░░░] 12/20 60%
Use █ (filled) and ░ (empty). No emoji or color icons.
Output format
Print the block below verbatim. If no in-flight tasks, omit the ── In-flight work ── section.
── Hyperflow Status ─────────────────────────────────────────
Version v3.0.0 (released 2026-05-16)
Profile fresh (analyzed 2h ago)
Memory 12 entries
Active tasks 2
── In-flight work ───────────────────────────────────────────
Task: implement-auth
Progress [███████████░░░░░░░░░] 8/14 57%
Last done T7: Reset email worker
Running T8: Login UI (Implementer · 14s elapsed)
Pending 6 sub-tasks
Tokens thinking 89.2k · worker 142.0k · total 231.2k
Wall-clock 4m 22s elapsed
ETA ~3m 16s remaining (avg 32s/sub-task · 6 left)
Task: fix-login-bug
Progress [░░░░░░░░░░░░░░░░░░░░] 0/3 0%
Status not started (created 8m ago, no dispatch run yet)
─────────────────────────────────────────────────────────────
When Profile is (missing), omit the (analyzed Xh ago) parenthetical.
When Version is (missing), print Version (missing).
When no .hyperflow/tasks/*.md files exist, omit the ── In-flight work ── section entirely; the snapshot block stands alone.
ETA computation
elapsed_seconds = now - started_unix
avg_per_subtask = elapsed_seconds / done
remaining_seconds = avg_per_subtask * pending
Format as Xm Ys or Hh Mm (skip zero leading units). Show (computing) when done < 3 — too few data points for a useful average.
If the task has multiple batches and the next batch is sequential per the planner output, multiply remaining by 1.1 to account for inter-batch synchronisation overhead.
Failure modes
Every section degrades gracefully:
- Missing git tags →
Version (missing) - Missing
.hyperflow/profile.md→Profile (missing) - Missing
.hyperflow/memory/index.md→Memory (none) - No
.hyperflow/tasks/*.mdfiles →Active tasks (none), no In-flight section - Task file present but Status block malformed/missing → fall back to checkbox count, show
(not tracked yet)for tokens/ETA Started:line absent →Status not started, skip ETA
Never error out. Never modify any file. Never dispatch an agent.
Doctrine
This skill has no Worker/Reviewer dispatch — it is a pure read. It does not count as a hyperflow run and does not append to memory. Output style follows output-style.md — no decorative icons, em-dash separators, plain status words.
Overview
/hyperflow:status prints a one-screen snapshot of the project's hyperflow state plus a live progress block for every in-flight task. Useful when picking up a session mid-flight, deciding whether to invoke /hyperflow:dispatch, or auditing whether a chain run is still healthy. Pure read — no agents, no writes, no chain side-effects.
Prerequisites
- Git repository (for the version line — degrades to
(missing)otherwise). .hyperflow/directory (for profile/memory/tasks lines — each section degrades to(missing)or(none)if absent).- No prerequisites for invocation itself — runs anywhere.
Instructions
See What to read and How to compute each field above for the full operational spec. Summary:
- Read version from latest git tag matching
v*. - Stat
.hyperflow/profile.mdfor freshness; bucket into fresh/stale/missing. - Count entries in
.hyperflow/memory/index.md. - Glob
.hyperflow/tasks/*.mdand parse each Status block for live progress. - Render the static snapshot block; render the In-flight block per task (if any).
- Stop. No prompts, no follow-ups.
Output
See Output format above for the exact block. Two sections — static snapshot and (if there are active tasks) In-flight work with per-task progress bar, last-done sub-task, currently-running sub-task, pending count, tokens, wall-clock, ETA.
Error Handling
| Failure | Behavior |
|---|---|
| Not a git repo | Version (missing); everything else still renders if .hyperflow/ exists. |
.hyperflow/profile.md missing | Profile (missing) (no parenthetical). |
.hyperflow/memory/index.md missing | Memory (none). |
| No task files | Omit the In-flight section entirely; just print the snapshot. |
| Task file with malformed Status block | Fall back to counting [x] vs [ ] checkboxes; show (not tracked yet) for tokens/ETA. |
stat flag differs between BSD (macOS) and GNU (Linux) | Try stat -f %m then fall back to stat -c %Y. |
Never errors out. Never modifies any file. Never dispatches an agent.
Examples
Healthy project, no active tasks
── Hyperflow Status ─────────────────────────────────────────
Version v3.1.2 (released 2026-05-16)
Profile fresh (analyzed 2h ago)
Memory 12 entries
Active tasks (none)
─────────────────────────────────────────────────────────────
Mid-dispatch with two active tasks
── Hyperflow Status ─────────────────────────────────────────
Version v3.1.2 (released 2026-05-16)
Profile fresh (analyzed 2h ago)
Memory 12 entries
Active tasks 2
── In-flight work ───────────────────────────────────────────
Task: implement-auth
Progress [███████████░░░░░░░░░] 8/14 57%
Last done T7: Reset email worker
Running T8: Login UI (Implementer · 14s elapsed)
Pending 6 sub-tasks
Tokens thinking 89.2k · worker 142.0k · total 231.2k
Wall-clock 4m 22s elapsed
ETA ~3m 16s remaining (avg 32s/sub-task · 6 left)
Task: fix-login-bug
Progress [░░░░░░░░░░░░░░░░░░░░] 0/3 0%
Status not started (created 8m ago, no dispatch run yet)
─────────────────────────────────────────────────────────────
Brand new install (no .hyperflow/ yet)
── Hyperflow Status ─────────────────────────────────────────
Version v3.1.2 (released 2026-05-16)
Profile (missing)
Memory (none)
Active tasks (none)
─────────────────────────────────────────────────────────────
Resources
- output-style.md — em-dash style, no decorative chars, plain status words.
- DOCTRINE.md — orchestration rules (status is exempt from per-step agent dispatch).
Frequently asked questions about Status
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
