AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Hyperflow Scope

skill-jeremylongshore-claude-code-plugins-plus-skills-hyperflow-scope · by jeremylongshore

Hyperflow planning phase. Use when a task is clear enough to decompose into batched steps before writing code — verbs like scope, decompose, "plan out", "break down", "plan this". Read-only with respect to source; writes a task file to .hyperflow/tasks/<slug>.md, then hands off to hyperflow-dispatch.

↗ Website ↗ Repository
— No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-jeremylongshore-claude-code-plugins-plus-skills-hyperflow-scope

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Hyperflow Scope? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

hyperflow-scope — decomposition phase (Antigravity single-agent)

Decompose, don't build. The only writes are to .hyperflow/. Follow the hyperflow doctrine.

Steps

  1. Research the affected surface (files to read/modify/create, conventions, test patterns). If the request is actually a design question, redirect to hyperflow-spec and stop.
  2. Produce a batch graph. Order batches topologically; each sub-task = one coherent change nameable in a single conventional-commit subject. Split any sub-task that touches >5 files, >500 LOC, spans 2+ subsystems, or would take a reviewer >10 min to grasp.
  3. Write .hyperflow/tasks/.md with: status table (progress, branch, commit cadence) → Goal → Why → Scope-at-a-glance table → Affected files (created/modified) → Execution plan (batch graph) → Batches (each sub-task with role, files, complexity, acceptance criteria, commit-message stub) → Verification plan.
  4. Print a one-line summary: Plan ready — .hyperflow/tasks/.md (N batches, M sub-tasks).
  5. Hand off: invoke the hyperflow-dispatch skill with the task slug.

Rules

  • No implementation code; no source edits.
  • Single-batch plans for multi-file work are an anti-pattern — decompose.
  • Always include a concrete verification plan.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Cloud & Infrastructure