Namespace routing primer (gsd:<namespace>, v1.40)
v1.40 ships six namespace meta-skills as the first-stage entry points for hierarchical routing — they keep the eager skill-listing token cost low (~120 tokens for 6 routers vs ~2,150 for a flat 86-skill listing) while every concrete sub-skill remains directly invocable. Each namespace router's body contains a routing table that maps your intent to the correct concrete sub-skill.
| Namespace | Router | Routes to |
|---|---|---|
| Phase pipeline | /gsd-workflow | discuss / plan / execute / verify / phase / progress |
| Project lifecycle | /gsd-project | milestones, audits, summary |
| Quality gates | /gsd-quality | code review, debug, audit, security, eval, ui |
| Codebase intelligence | /gsd-context | map, graphify, docs, learnings |
| Management | /gsd-manage | config, workspace, workstreams, thread, update, ship, inbox |
| Exploration & capture | /gsd-ideate | explore, sketch, spike, spec, capture |
You almost never need to type a namespace router yourself. Their value is in the routing layer the model uses to discover the right sub-skill — they exist so the system prompt can list 6 entries instead of 86. If you already know the concrete command (e.g. /gsd-plan-phase), call it directly.