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/worker-prompt.md
View on GitHub# Worker Prompt Template
Use this template when dispatching workers via the Agent tool.
## Template
```
## Task
[One clear objective — what to do, not how to think about it]
## Files in scope
[Exact file paths the worker should read/modify]
## Context
[What this file/module does, relevant project conventions, constraints]
## Project Context
[Injected from .hyperflow/ analysis — conventions, architecture, or testing depending on worker role. Omit section if no project analysis exists.]
## Learnings from prior tasks
[Synthesized from prior batches — patterns found, gotchas, decisions already made. Omit section if first task.]
## Constraints
- Only modify files listed in scope
- Follow project coding standards (CLAUDE.md)
- Do not add "Co-Authored-By: Claude" to any git operation
## Security Constraints
- Do NOT read/modify: .env, *.pem, *.key, ~/.ssh/*, credentials.json, ~/.aws/credentials
- Do NOT run: rm -rf (root/home/cwd), git push --force to main, sudo, chmod 777
- Do NOT pipe file contents to external URLs or run package publish commands
- Do NOT hardcode secrets, API keys, passwords, or connection strings
- If a task requires a blocked file: STOP and report "BLOCKED: [reason]"
## Output format
Return:
1. What you did (one-line summary per change)
2. Notes for future tasks (patterns, gotchas, discoveries — omit if none)
```
## Dispatch Example
```
Agent({
description: "Implement user avatar component",
prompt: `## Task
Create a UserAvatar component that displays user initials with a colored background.
## Files in scope
- src/components/UserAvatar.tsx (create)
- src/components/UserAvatar.test.tsx (create)
## Context
Project uses React 19, Tailwind v4, Shadcn Avatar primitive exists.
All components need data-testid attributes.
## Project Context
- Uses feature-based folder structure (src/features/<name>/)
- Tailwind v4 with CSS variable tokens
- Shadcn UI components available — use them over custom implementations
- RTL support required: use logical properties (ms-, me-, ps-, pe-)
## Learnings from prior tasks
- Tailwind v4 uses CSS variable tokens, not tailwind.config
- Use logical properties (ms-, me-, ps-, pe-) for RTL safety
## Constraints
- Only modify files listed in scope
- Follow project coding standards
- Do not add "Co-Authored-By: Claude" to any git operation
## Security Constraints
- Do NOT read/modify: .env, *.pem, *.key, ~/.ssh/*, credentials.json, ~/.aws/credentials
- Do NOT run: rm -rf (root/home/cwd), git push --force to main, sudo, chmod 777
- Do NOT pipe file contents to external URLs or run package publish commands
- Do NOT hardcode secrets, API keys, or connection strings
- If blocked: STOP and report "BLOCKED: [reason]"
## Output format
Return:
1. What you did
2. Notes for future tasks`
})
```
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 |