Status
Use when the user wants a one-screen view of current hyperflow project state, version...
Install
npx skills add jeremylongshore/tons-of-skills-marketplace --skill status -g -a claude-code -y- Repository
- jeremylongshore/tons-of-skills-marketplace2.9k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,916 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user wants a one-screen view of current hyperflow project state, version, profile freshness, memory count, and live progress on every in-flight task. Read-only; never modifies state, never dispatches workers. Trigger with /hyperflow:status, "what is hyperflow doing", "show task progress", "where are we".
Status
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):
