Skill2.9k estrellas del repoactualizado 6d ago

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.

Ver fuente Repositorio: tons-of-skills-marketplace

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/hyperflow-status && cp -r /tmp/hyperflow-status/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-status ~/.claude/skills/hyperflow-status

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# 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.

Del mismo repositorio

agency-osSkill

apexSkill

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

apex-planSkill

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

apex-reconSkill

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

apex-reviewSkill

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

apex-statusSkill

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

apex-takeoverSkill

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

atlasSkill

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.