jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/hyperflow/skills/dispatch
dispatch
FlaggedUse when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it", "run the batches".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 50.8 KB |
| references/examples.md | markdown | 5.9 KB |
| references/git-workflow.md | markdown | 5.9 KB |
| references/memory-system.md | markdown | 15.3 KB |
| references/output-style.md | markdown | 8.2 KB |
| references/quality-gates.md | markdown | 1.9 KB |
| references/review-levels.md | markdown | 4.4 KB |
| references/reviewer-prompt.md | markdown | 3.7 KB |
| references/worker-prompt.md | markdown | 2.7 KB |
references/output-style.md
View on GitHub# Output Style Guide
Every Hyperflow output follows this visual language. Calm, elegant, no decorative icons. Em-dash, lowercase descriptions, and box-drawing rules for section separators only.
## Allowed Characters
| Symbol | Use |
|---|---|
| `—` | Em-dash separator between role/label and description |
| `·` | Subtle separator in inline lists (e.g. `pass · skipped · pass`) |
| `─` | Horizontal rule for top/bottom of summary blocks |
| `│├└` | Tree connectors in flow diagrams |
## Banned Characters
These must **never** appear in user-facing output:
`⚡` `✓` `✗` `▸` `→` `•` (as bullet prefix) `🚀` `📦` `⚠️` `🟢` `🔴` `*` (when used as a label prefix)
The only exception: code blocks may contain whatever the user's code contains. Banned-char rules apply to status lines, agent labels, summaries, and any text the skill outputs directly.
## 1. Session Banner
```
Hyperflow v1.12.1
```
One line. Version only.
## 2. Update Notification
```
Hyperflow update available — v1.12.1 → v1.13.0
run: claude plugin update hyperflow@hyperflow-marketplace
```
Em-dash between phrase and version delta. Install hint indented two spaces, no icon prefix.
## 3. Analysis Cache Status
### Fresh (skip)
```
Analysis cache fresh — skipping
```
### Partial refresh
```
Refreshing — profile.md, dependencies.md
```
### Full analysis
```
Analyzing project — 6 searchers in parallel
Cached — no incomplete tasks
```
### Incomplete tasks found
```
Incomplete tasks from prior session:
implement-auth.md 3/5 sub-tasks done
fix-login-bug.md 1/3 sub-tasks done
```
Two-space indent, no bullet prefix.
## 4. Agent Dispatch Labels
Every agent dispatch gets a label **before** the Agent tool call. Format:
```
<Role> — <short lowercase description>
```
**Reviewer and Debugger roles** wrap in `**bold**`:
```
**Reviewer** — reviewing auth middleware output
**Debugger** — investigating test failure in auth.test.ts
```
**Worker roles** (Implementer, Searcher, Writer) stay plain:
```
Implementer — creating auth middleware
Searcher — finding related test files
Writer — generating API documentation
```
### Parallel / serial dispatch (2+ agents in same batch)
Header line declares **intent** (`parallel:N` or `serial:N`). Footer line proves **execution** (wall-clock vs cumulative · ratio). The ratio is what catches a batch that *was supposed to* run parallel but actually ran serial.
**Parallel batch** (all N dispatches in one message):
```
Batch 1 — parallel:3 · standard profile · L1–L2
Searcher — analyse existing auth patterns
Implementer — write middleware + route guards
Writer — generate test suite for auth
wall-clock: 47s · cumulative: 2m 18s · ratio 0.34 — parallel
```
**Serial batch** (depends on a prior batch's output):
```
Batch 2 — serial:1 · depends on Batch 1
Implementer — wire routes (with batch 1 learnings)
wall-clock: 31s · cumulative: 31s · ratio 1.0 — serial (single agent)
```
**Ratio interpretation:**
| Ratio | Meaning |
|---|---|
| `≤ 0.5` | True parallel — `max(t_i)` dominates `sum(t_i)` |
| `0.5 – 0.8` | Mixed — partial overlap, some serial gates |
| `≥ 0.8` | Effectively serial — if the label said `parallel:N` this is a doctrine violation (see DOCTRINE red flags) |
| `1.0` | Pure serial — expected only when N = 1 or batch declared `serial:N` |
Rules:
- Role left-padded to the longest role in the block (typically 13 chars for `Implementer`).
- Description starts after the em-dash, lowercased.
- Single-agent dispatch — header still printed (`serial:1`) but the footer is optional.
- `wall-clock` is the elapsed real time from first `Agent()` call to last `⎿ Done`. `cumulative` is the sum of the individual agent durations reported in each `⎿ Done (... · Ym Zs)`.
## 5. Agent Progress
For long batches (3+ agents, multi-minute), print a running indicator with middle dots:
```
running··· done
```
Skip for single-agent or fast dispatches.
## 6. Quality Gates
Single line, all gates separated by middle dots:
```
gates — lint: pass · typecheck: pass · tests: pass · build: pass
```
On failure:
```
gates — lint: pass · typecheck: fail · tests: skipped · build: skipped
typecheck: 3 errors in src/auth/middleware.ts
```
Use `pass` / `fail` / `skipped` as plain words. No `✓` / `✗` / `—`. Detail lines indented two spaces.
## 7. Usage Summary
Printed after every completed task. The summary surfaces `Wall-clock` and `Cumulative` rows so parallelism is provable from the numbers alone — without trusting the dispatch labels.
```
── Hyperflow Usage ─────────────────────────────────────────
Triage 1 agent 1.8k tokens
Spec depth: standard 1 agent 3.2k tokens
Profile: deep — —
Agents 12 agents 238.2k tokens
Wall-clock 3m 47s
Cumulative 14m 22s (ratio 0.26 — parallel)
Escalations 0
Total 14 agents 243.1k tokens
────────────────────────────────────────────────────────────
```
`ratio = wall-clock / cumulative`. Lower is better for parallelism. The annotation after the ratio is one of `parallel` (≤ 0.5) / `mixed` (0.5–0.8) / `serial` (≥ 0.8) per the table in §4.
Backwards-compat: the shorter form (no Wall-clock / Cumulative rows) is acceptable for tasks with a single batch or a single agent — there's nothing to parallelise. For tasks with 2+ batches OR 2+ parallel-eligible workers, the two rows MUST appear.
Shorter example (single-batch task):
```
── Usage ─────────────────────────────────────────
11 agents 234.1k tokens
──────────────────────────────────────────────────
```
Rules:
- Top/bottom rules — `──` repeated to ~50 chars
- Agent counts right-aligned in 3-char column
- Token counts right-aligned in 7-char column, formatted as `Xk` or `X.Xk`
- Breakdown after tokens (optional): `(3 reviewers: 38.4k · 1 final: 13.7k)` — middle dots between items
## 8. Section Headers
Lowercase bracketed labels for structured multi-line blocks only:
```
[layers]
[skills]
[detection]
[memory]
[gates]
[capabilities]
```
Use sparingly. Never use as a decorative prefix on a single status line.
## 9. Memory Output
```
[memory] location: .hyperflow/memory/
1 hot auth uses JWT RS256, not HS256 (tags: auth, security)
2 hot zod is project-wide validation (tags: validation, zod)
3 warm Postgres uses UTC timestamps (tags: db, conventions)
```
Entry number two-space indent. Tier as plain word (`hot` / `warm` / `cold`), no brackets. Tags in parens at end.
## 10. Task File Status
When creating/updating task files:
```
Task: implement-auth (3 sub-tasks)
Write auth middleware pending
Add route guards pending
Generate test suite pending
```
After completion:
```
Task complete — implement-auth (3/3)
```
No bullet prefixes. Status word right-padded for column alignment.
## 11. Security Violations
```
SECURITY VIOLATION — hardcoded API key in src/config.ts:42
Pipeline halted, review required
```
## 12. Blocked Resources
```
BLOCKED — worker attempted to read .env
File is in security blocklist
```
## Formatting Rules
1. **No prose between outputs.** Status lines only. No "I'm now going to…" or "Let me…".
2. **Alignment matters.** Pad roles, model names, and counts for columnar alignment.
3. **One blank line** between different output sections (e.g., between agent labels and gates).
4. **No trailing summaries.** The usage block IS the summary. Don't add "Done! I completed X."
5. **No decorative chars.** Em-dash for separators, middle dots for inline lists. Never `⚡`, `✓`, `✗`, `▸`, `→`, etc.
6. **Bold for Reviewer and Debugger.** Only `**Reviewer**` and `**Debugger**` are bolded. Workers stay plain.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |