workflow-routing — скилл для Claude Code: маршрутизация задач
Скилл workflow-routing выбирает между Superpowers и GSD с учётом состояния проекта и масштаба задачи. Он срабатывает перед другими скиллами и командами GSD, когда установлены обе системы.
MIT ★ 328 обновлён 2026-10-29
npx skills add coco-research/coco --skill workflow-routing -a claude-codeЧто делает workflow-routing
Перед выбором инструмента скилл проверяет проект: для активного GSD нужны .planning/PROJECT.md, .planning/ROADMAP.md и .planning/STATE.md. Задачу в рамках текущей фазы он направляет в GSD; небольшую или несвязанную — в /gsd:quick. Если GSD не активен, выбор зависит от масштаба: многоэтапный проект ведёт к /gsd:new-project, задача на одну сессию — к Superpowers.
Для отладки и планирования предусмотрены отдельные развилки. Например, баг текущей фазы направляется в /gsd:debug, а задачу без GSD с неясным масштабом предлагается сначала разобрать через /brainstorming. В больших проектах GSD отвечает за фазы и состояние, Superpowers — за практики вроде TDD, отладки и ревью.
Скилл должен запускаться первым, когда установлены обе системы. Если в рабочей директории нет .planning/ и ROADMAP.md, он не считает GSD активным.
Какие задачи решает
- выбрать GSD или Superpowers для новой задачи
- направить баг в подходящий инструмент отладки
- понять, нужна ли проекту многоэтапная структура
- согласовать планирование с текущей фазой GSD
Примеры запросов агенту
- Определи, вести эту задачу через GSD или Superpowers.
- Разбери баг с учётом текущей фазы проекта.
- Выбери способ планирования для этой многоэтапной функции.
Как установить workflow-routing
1Через Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a claude-code2Вручную: положить файлы
~/.claude/skills/workflow-routing/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/workflow-routing/
1Через Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a codex2Вручную: положить файлы
.agents/skills/workflow-routing/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a cursor2Вручную: положить файлы
.cursor/skills/workflow-routing/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install coco-research/coco skills/workflow-routing2Вручную: положить файлы
.github/skills/workflow-routing/SKILL.md1Через Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a gemini-cli2Командой платформы
gemini skills install https://github.com/coco-research/coco --path skills/workflow-routingВручную: положить файлы
.devin/skills/workflow-routing/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о workflow-routing
Как установить workflow-routing в Claude Code?
Выполните npx skills add coco-research/coco --skill workflow-routing -a claude-code. Файл скилла находится по пути ~/.claude/skills/workflow-routing/SKILL.md.
Что делает workflow-routing?
Проверяет состояние проекта и масштаб задачи, затем выбирает маршрут между командами GSD и скиллами Superpowers. При наличии обеих систем запускается перед остальными.
Как workflow-routing определяет, активен ли GSD?
Скилл проверяет .planning/PROJECT.md, .planning/ROADMAP.md и .planning/STATE.md. Для проекта без активного GSD маршрут выбирается по масштабу задачи.
Исходный текст
SKILL.md · MIT
---
name: workflow-routing
description: "Use when starting any task, before invoking any other skill or GSD command, to route between Superpowers skills and GSD commands from project state and task scope. Fires first when both systems are installed."
domain: foundational
---
# Workflow Routing: Superpowers + GSD
**Announce at start:** "Workflow Routing skill activated."
Route every task to the right toolchain. Superpowers handles **task-level quality** (TDD, debugging, design, review). GSD handles **project-level orchestration** (phases, milestones, persistent state). They are complementary — never competing.
<HARD-GATE>
Check routing BEFORE invoking any other skill or GSD command. This skill fires first.
</HARD-GATE>
## Detection: Is GSD Active?
Check the current working directory:
```dot
digraph detect {
".planning/ exists?" [shape=diamond];
"ROADMAP.md exists?" [shape=diamond];
"GSD ACTIVE" [shape=box, style=filled, fillcolor=lightblue];
"GSD NOT ACTIVE" [shape=box, style=filled, fillcolor=lightyellow];
".planning/ exists?" -> "ROADMAP.md exists?" [label="yes"];
".planning/ exists?" -> "GSD NOT ACTIVE" [label="no"];
"ROADMAP.md exists?" -> "GSD ACTIVE" [label="yes"];
"ROADMAP.md exists?" -> "GSD NOT ACTIVE\n(stale or pre-roadmap)" [label="no"];
}
```
**GSD active signals:** `.planning/PROJECT.md`, `.planning/ROADMAP.md`, `.planning/STATE.md` all present.
## Primary Routing Decision
```dot
digraph route {
"Task received" [shape=doublecircle];
"GSD active?" [shape=diamond];
"Task in current phase scope?" [shape=diamond];
"Scope: multi-phase?" [shape=diamond];
"Use GSD commands" [shape=box, style=filled, fillcolor=lightblue];
"Use /gsd:quick" [shape=box, style=filled, fillcolor=lightcyan];
"Suggest /gsd:new-project" [shape=box, style=filled, fillcolor=lightblue];
"Use Superpowers skills" [shape=box, style=filled, fillcolor=lightyellow];
"Task received" -> "GSD active?";
"GSD active?" -> "Task in current phase scope?" [label="yes"];
"GSD active?" -> "Scope: multi-phase?" [label="no"];
"Task in current phase scope?" -> "Use GSD commands" [label="yes"];
"Task in current phase scope?" -> "Use /gsd:quick" [label="no, small/unrelated"];
"Scope: multi-phase?" -> "Suggest /gsd:new-project" [label="yes"];
"Scope: multi-phase?" -> "Use Superpowers skills" [label="no"];
}
```
## Scope Signals
| Signal | Indicates | Route |
|--------|-----------|-------|
| "build app", "create platform", "new project", "implement system" | Multi-phase | GSD |
| "phase", "milestone", "roadmap", "epic", "release" | Multi-phase | GSD |
| 6+ features, 2+ weeks, architectural decisions needed | Multi-phase | GSD |
| "fix bug", "add button", "update function", "refactor method" | Single-session | Superpowers |
| "quick fix", "hotfix", "one more thing" | Small/ad-hoc | Superpowers or `/gsd:quick` if GSD active |
| Unknown scope, user unsure | Undetermined | `/brainstorming` first to scope, then decide |
## Combined Workflows
### Multi-Phase Project (GSD + Superpowers for Quality)
```
/brainstorming ← Superpowers: design before planning
↓
/gsd:new-project ← GSD: project structure + roadmap
↓
/gsd:plan-phase N ← GSD: detailed phase plan
↓
/gsd:execute-phase N ← GSD: runs tasks with atomic commits
├── /systematic-debugging ← Superpowers: if bug during execution
└── /test-driven-development ← Superpowers: TDD within each task
↓
/requesting-code-review ← Superpowers: review before moving on
↓
/gsd:verify-work N ← GSD: UAT validation
↓
/verification-before-completion ← Superpowers: evidence-based "done"
↓
/gsd:progress ← GSD: route to next phase
```
### Single-Session Task (Superpowers Only)
```
/brainstorming ← Explore intent, produce spec
↓
/writing-plans ← Break into TDD tasks
↓
/executing-plans ← Run tasks sequentially
OR /subagent-driven-development ← Run tasks via parallel subagents
├── /systematic-debugging ← If issues arise
└── /test-driven-development ← TDD per task
↓
/requesting-code-review ← Review before done
↓
/verification-before-completion ← Prove it works
↓
/finishing-a-development-branch ← Merge, PR, or cleanup
```
## Edge Case Decision Trees
### "Debug this" — Which Tool?
```dot
digraph debug {
"Bug reported" [shape=doublecircle];
"GSD active?" [shape=diamond];
"Bug related to current phase?" [shape=diamond];
"Will span multiple sessions?" [shape=diamond];
"/gsd:debug" [shape=box, style=filled, fillcolor=lightblue];
"/systematic-debugging" [shape=box, style=filled, fillcolor=lightyellow];
"Bug reported" -> "GSD active?";
"GSD active?" -> "Bug related to current phase?" [label="yes"];
"GSD active?" -> "Will span multiple sessions?" [label="no"];
"Bug related to current phase?" -> "/gsd:debug" [label="yes"];
"Bug related to current phase?" -> "/systematic-debugging\nthen /gsd:quick to commit" [label="no"];
"Will span multiple sessions?" -> "/gsd:debug" [label="yes, need persistence"];
"Will span multiple sessions?" -> "/systematic-debugging" [label="no, fix it now"];
}
```
### "Plan this" — Which Tool?
```dot
digraph plan {
"Planning requested" [shape=doublecircle];
"GSD active?" [shape=diamond];
"Feature in roadmap?" [shape=diamond];
"/gsd:plan-phase N" [shape=box, style=filled, fillcolor=lightblue];
"/gsd:add-phase or /gsd:quick" [shape=box, style=filled, fillcolor=lightcyan];
"/brainstorming then /writing-plans" [shape=box, style=filled, fillcolor=lightyellow];
"Planning requested" -> "GSD active?";
"GSD active?" -> "Feature in roadmap?" [label="yes"];
"GSD active?" -> "/brainstorming then /writing-plans" [label="no"];
"Feature in roadmap?" -> "/gsd:plan-phase N" [label="yes, phase N"];
"Feature in roadmap?" -> "/gsd:add-phase or /gsd:quick" [label="no"];
}
```
### Scope Escalation (Superpowers → GSD)
During `/brainstorming`, if scope grows beyond single-session:
```
Detection:
- 5+ independent subsystems identified
- 2+ weeks estimated work
- Multiple architectural decisions needed
- User says "this is bigger than I thought"
Action:
"This needs GSD's phase structure for persistence across sessions.
Ready to initialize /gsd:new-project with the spec we just brainstormed?"
→ Convert brainstorming output into GSD project input
→ User confirms escalation
```
### User Picks Wrong Tool
**User wants Superpowers for a large project:**
> "This sounds like it needs 5+ phases and multiple sessions. GSD would give you persistent state and milestone tracking. Want to use `/gsd:new-project` instead?"
**User wants GSD for a tiny task:**
> "This is small enough for a single session — GSD's ceremony would slow us down. Let's use `/brainstorming` → `/writing-plans` → `/executing-plans` instead."
**Always respect the user's final choice.** Suggest, don't force.
## Universal Rules (Both Toolchains)
1. **Always `/brainstorming` before creative work** — regardless of GSD or Superpowers
2. **Always `/verification-before-completion` before claiming done** — no exceptions
3. **Always `/requesting-code-review` after significant implementation** — works in both contexts
4. **Always `/test-driven-development` when writing code** — embedded discipline, not optional
5. **Always `/systematic-debugging` before proposing fixes** — root cause first
## Quick Reference: Command Mapping
| Task | GSD Active | No GSD |
|------|-----------|--------|
| Design a feature | `/brainstorming` → `/gsd:plan-phase` | `/brainstorming` → `/writing-plans` |
| Execute a plan | `/gsd:execute-phase N` | `/executing-plans` or `/subagent-driven-development` |
| Fix a bug (small) | `/gsd:quick` | `/systematic-debugging` |
| Fix a bug (complex) | `/gsd:debug` | `/systematic-debugging` |
| Review code | `/requesting-code-review` | `/requesting-code-review` |
| Verify work | `/gsd:verify-work N` | `/verification-before-completion` |
| Check progress | `/gsd:progress` | N/A (session-scoped) |
| Resume paused work | `/gsd:resume-work` | Re-read plan file |
| Ad-hoc task | `/gsd:quick` | Direct Superpowers workflow |
| Start new project | `/gsd:new-project` | `/brainstorming` → `/writing-plans` |
## Red Flags — You're Routing Wrong
| Symptom | Problem | Fix |
|---------|---------|-----|
| Using `/writing-plans` when `.planning/` exists | Bypassing GSD's plan structure | Use `/gsd:plan-phase` instead |
| Using `/gsd:new-project` for a 1-hour task | Overkill, ceremony slows you down | Use Superpowers workflow |
| Skipping `/brainstorming` because "it's obvious" | Hidden assumptions will bite you | Brainstorm first, always |
| Fixing bugs without `/systematic-debugging` | Guessing instead of investigating | Root cause first |
| Claiming "done" without verification evidence | No proof = no done | Run `/verification-before-completion` |
| Using Superpowers for multi-week work | Context lost between sessions | Escalate to GSD |
| Ignoring stale GSD project in directory | `.planning/` exists for a reason | Run `/gsd:progress` to check state |
© coco-research · MIT · coco-research/coco