workflow-routing — Claude Code skill for task routing
The workflow-routing skill chooses between Superpowers and GSD based on project state and task scope. It runs before other skills or GSD commands when both systems are installed.
MIT ★ 328 updated 2026-10-29
npx skills add coco-research/coco --skill workflow-routing -a claude-codeWhat workflow-routing does
The skill checks for .planning/PROJECT.md, .planning/ROADMAP.md, and .planning/STATE.md to identify an active GSD project. Work within the current phase goes to GSD commands; a small, unrelated task can go to /gsd:quick. Without active GSD, a multi-phase effort points to /gsd:new-project, while a single-session task goes to Superpowers.
Debugging and planning have their own routing branches. A bug tied to the current phase goes to /gsd:debug; when the scope is unclear and GSD is inactive, the suggested first step is /brainstorming. GSD handles phases and persistent project state, while Superpowers covers task-level practices such as TDD, debugging, and review.
When both systems are installed, this skill is meant to run first. Without .planning/ and ROADMAP.md in the working directory, it treats GSD as inactive.
What it helps with
- choose GSD or Superpowers for a new task
- route a bug to the right debugging workflow
- decide whether work needs multiple project phases
- match planning commands to the current GSD phase
Example prompts for the agent
- Choose whether this task belongs in GSD or Superpowers.
- Route this bug based on the project's current phase.
- Pick a planning workflow for this multi-phase feature.
How to install workflow-routing
1Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a claude-code2Manually: put the files in place
~/.claude/skills/workflow-routing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/workflow-routing/
1Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a codex2Manually: put the files in place
.agents/skills/workflow-routing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a cursor2Manually: put the files in place
.cursor/skills/workflow-routing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install coco-research/coco skills/workflow-routing2Manually: put the files in place
.github/skills/workflow-routing/SKILL.md1Skills CLI (Vercel)
npx skills add coco-research/coco --skill workflow-routing -a gemini-cli2Platform CLI
gemini skills install https://github.com/coco-research/coco --path skills/workflow-routingManually: put the files in place
.devin/skills/workflow-routing/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about workflow-routing
How do I install workflow-routing in Claude Code?
Run npx skills add coco-research/coco --skill workflow-routing -a claude-code. The skill file is at ~/.claude/skills/workflow-routing/SKILL.md.
What does workflow-routing do?
It checks project state and task scope, then directs work to GSD commands or Superpowers skills. When both systems are installed, it runs before the other tools.
How does workflow-routing detect an active GSD project?
It checks for .planning/PROJECT.md, .planning/ROADMAP.md, and .planning/STATE.md. If GSD is inactive, it routes based on the task's scope.
Source text
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