By name: protocol-router description: Use when a request needs specialist routing before implementation, including bugs, feature work, architecture changes, UX work, security-sensitive changes, or tc-backed delivery planning.
Protocol Router
Use this skill to classify the request and choose the right specialist flow before coding.
Classification
| Request type | Start with |
|---|---|
| bug, regression, test failure | qa |
| backend feature, refactor, architecture, performance | ta |
| user-facing feature, workflow, product experience | sd or uxd |
| physical product, connected product, hardware/software touchpoint | ind |
| visual polish, design system, component styling | uids or uid |
| auth, permissions, secrets, trust boundaries | sec in addition to primary flow |
| docs, onboarding, references | doc |
| deploy, CI, env, infrastructure | do |
Codex rule
If the user did not explicitly ask for subagents, apply the specialist lens in the main session.
If the user explicitly asked for delegation or parallel work, you may spawn subagents after deciding:
- what the immediate local step is
- which work can safely run in parallel
Standard flow
- classify the request
- identify the specialist sequence
- check whether a
tcPRD or task exists - create missing task records if the work is substantial
- execute the specialist flow
- verify with
qabefore closing implementation work
Routing patterns
- bug:
qa -> me -> qa - backend feature:
ta -> me -> qa - experience feature:
sd -> uxd -> uids -> uidas needed, thenta -> me -> qa - physical-digital feature:
ind -> sd -> uxd -> uids -> uidas needed, thenta -> me -> qa - security-sensitive feature: primary flow plus
secbefore completion - infrastructure:
do -> me -> qa
References
Read references/routing-matrix.md when you need the full mapping.