菜单
Route every user request to read-only exploration, single-agent work, full Composer swarm, or GitHub issue flow before spending tokens or spawning leaves.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Keep coordinator and leaf context lean-batch reads, cap logs, use execute_code to filter-so swarms stay fast and within token limits.
Use at the start of non-trivial software tasks. Gather repo ground truth with batched reads and searches before planning or delegate_task.
Obey Plan 1A hook session phases so mutating tools, delegate_task sizing, and re-planning do not waste turns or trigger blocks.
Use when spawning delegate_task leaves for coding work. Pack self-contained goals and context so parallel Composer workers ship verifiable patches without coordinator chat history.
Require structured candidate-result JSON from swarm leaves so critique_candidates.py and synthesis run on evidence, not prose self-reports.
Enrich slim hook-injected delegate_tasks with touch map, failure excerpts, and verification commands so parallel leaves produce verifiable patches without coordinator chat history.
| name | heavy-scope-router |
| description | Route every user request to read-only exploration, single-agent work, full Composer swarm, or GitHub issue flow before spending tokens or spawning leaves. |
| version | 0.1.0 |
| author | CodeGraphTheory |
| license | MIT |
| metadata | {"hermes":{"tags":["heavy-coder","triage","performance","coordinator"],"related_skills":["heavy-explore-first","heavy-team-default","heavy-single-mode","heavy-issue-to-merge"]}} |
Wrong routing is the most expensive mistake: eight parallel leaves on a repo audit, or solo edits on a cross-cutting refactor. This skill runs first on every non-trivial turn and picks the cheapest path that still satisfies the user.
Load this skill before heavy-team-default unless the user already pinned a mode.
User message
├─ Explicit single mode / composer only / no team? → heavy-single-mode
├─ GitHub issue #N, PR, claim, publish (no local code yet)? → heavy-issue-to-merge
├─ Read-only intent (no "implement", "fix", "add", "ship", "patch")?
│ → heavy-explore-first; NO delegate_task unless user then asks to implement
├─ Trivial one-liner (typo path given, single obvious edit)?
│ → suggest single mode OR one coordinator fix; hooks may still council - user can say single mode
└─ Non-trivial code change → heavy-team-default + companion skills (enrich → dispatch → synthesize → ship)
Treat as explore-only when the user wants:
Done when: you have batched reads/searches and a written answer; you have not called delegate_task.
Treat as swarm path when the user wants:
Done when: heavy-scope-router hands off to heavy-pre-dispatch-enrich or hook-injected plan + heavy-swarm-dispatch.
| Mistake | Cost | Router rule |
|---|---|---|
| Width-8 swarm for audit | 8× leaf tokens | Read-only branch |
| Re-plan after injection | Extra coordinator turns | heavy-swarm-dispatch |
| Solo edit on risky refactor | Bad patch | Swarm branch unless single mode |
heavy-team-default