Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-dispatch

hyperflow-dispatch

Verified

Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire up", "run the plan", "execute the task". Works batches sequentially with self-review and per-task commits. In Antigravity there is no sub-agent fan-out — the single agent does each batch itself.

hyperflow-dispatch — execution phase (Antigravity single-agent)

Execute the task file from hyperflow-plan. No sub-agent dispatch and no model tiers in Antigravity — you do each batch yourself, then self-review before committing. Follow the hyperflow doctrine.

Per batch

  1. Implement every sub-task in the batch (sequentially; they were planned as small, independent units).
  2. Self-review the batch diff against the level checklist:
    • L1 syntax/format/obvious bugs · L2 spec compliance, naming, edge cases · L3 cross-file integration + security (secrets, injection, validation).
    • Elevate to L3 when the change touches auth, data, or external input. Fix anything found before committing.
  3. Quality gates on affected files: run the project's lint, typecheck, and tests. Fix failures (never --no-verify).
  4. Commit per sub-task — one sub-task = one conventional commit (respect commitlint: lowercase subject, allowed scope). Stage only that sub-task's files; never commit files you didn't change.
  5. Update the task file's status block (tick the sub-task, bump progress) and append any durable learning to .hyperflow/memory/.

After all batches

  1. Final integration self-review over the cumulative diff — catch cross-batch contradictions, scope leaks, and any/type regressions.
  2. End gate via AskUserQuestion: offer to run hyperflow-audit (independent review) and/or hyperflow-deploy. Both are binary (no recommended marker). Never auto-push.

Rules

  • A SECURITY_VIOLATION halts immediately — no commit, no continue.
  • If the working tree is dirty with files you didn't create (concurrent work), never stage them; re-check git status before each commit.
  • Auto mode completes every sub-task before any summary — no partial "to resume" hand-offs.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall