Workflow Routing Agent Skill

Use at the start of any task to route between Superpowers skills and GSD commands based on project state, task scope, and context signals. Fires before other skills when both systems are installed.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

196

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/coco-research/coco --skill workflow-routing

The instruction itself

15 sections, as written by the author

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:

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

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?

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?

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)

Always /brainstorming before creative work — regardless of GSD or Superpowers
Always /verification-before-completion before claiming done — no exceptions
Always /requesting-code-review after significant implementation — works in both contexts
Always /test-driven-development when writing code — embedded discipline, not optional
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 |

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens

Domain Name Brainstormer

by frostant

×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts

Scientific Brainstorming

by christophacham

×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens

GitHub Project Management

by ComeOnOliver

×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take coco-research/workflow-routing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.