Protocol — Expert Team Router
Purpose
Route to a named protocol (expert panel). Each protocol is a fixed roster of domain experts that work on whatever task the user provides.
Instructions
Parse Input
The user invokes: /protocol <name> <task>
- If no arguments: list available protocols (see below) and stop.
- If only a name with no task: ask "What should Protocol work on?"
- If name + task: dispatch to the matching protocol skill.
Available Protocols
| Protocol |
Skill |
Roster |
| brains |
protocol-brains |
2 Database, 2 TypeScript architects, 1 Legacy Migration, 1 React, 1 Test, 1 Monorepo, 2 Multiagent workflow, 1 Orchestration |
| pinky |
protocol-pinky |
2 React architects, 1 TS architect, 1 State/Data, 1 MUI, 1 UX/a11y, 1 Contracts, 1 Test, 1 i18n, 1 Security, 1 Performance, 1 Business Impact, 1 Backend Contract, 1 Monorepo, 1 Tailwind, 1 UI Component Library |
Dispatch
Invoke the matching skill using:
Skill: protocol-<name>, args: "<task>"
If the protocol name is not recognized, say:
"Unknown protocol: <name>. Available protocols: brains, pinky"
Output (when listing)
## Available Protocols
| Protocol | Experts |
|----------|---------|
| **brains** | 2 Database, 2 TS architects, 1 Legacy Migration, 1 React, 1 Test, 1 Monorepo, 2 Multiagent workflow, 1 Orchestration |
| **pinky** | 2 React architects, 1 TS architect, 1 State/Data, 1 MUI, 1 UX/a11y, 1 Contracts, 1 Test, 1 i18n, 1 Security, 1 Performance, 1 Business Impact, 1 Backend Contract, 1 Monorepo, 1 Tailwind, 1 UI Component Library |
Usage: /protocol <name> <task>
1---2name: protocol3description: Launch a named expert protocol. Usage: /protocol [name] [task]. Run /protocol with no args to list available protocols.4---56# Protocol — Expert Team Router78## Purpose910Route to a named protocol (expert panel). Each protocol is a fixed roster of domain experts that work on whatever task the user provides.1112## Instructions1314### Parse Input1516The user invokes: `/protocol <name> <task>`1718- If no arguments: list available protocols (see below) and stop.19- If only a name with no task: ask "What should Protocol <Name> work on?"20- If name + task: dispatch to the matching protocol skill.2122### Available Protocols2324| Protocol | Skill | Roster |25| --------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |26| **brains** | `protocol-brains` | 2 Database, 2 TypeScript architects, 1 Legacy Migration, 1 React, 1 Test, 1 Monorepo, 2 Multiagent workflow, 1 Orchestration |27| **pinky** | `protocol-pinky` | 2 React architects, 1 TS architect, 1 State/Data, 1 MUI, 1 UX/a11y, 1 Contracts, 1 Test, 1 i18n, 1 Security, 1 Performance, 1 Business Impact, 1 Backend Contract, 1 Monorepo, 1 Tailwind, 1 UI Component Library |2829### Dispatch3031Invoke the matching skill using:3233```34Skill: protocol-<name>, args: "<task>"35```3637If the protocol name is not recognized, say:3839> "Unknown protocol: `<name>`. Available protocols: brains, pinky"4041## Output (when listing)4243```44## Available Protocols4546| Protocol | Experts |47|----------|---------|48| **brains** | 2 Database, 2 TS architects, 1 Legacy Migration, 1 React, 1 Test, 1 Monorepo, 2 Multiagent workflow, 1 Orchestration |49| **pinky** | 2 React architects, 1 TS architect, 1 State/Data, 1 MUI, 1 UX/a11y, 1 Contracts, 1 Test, 1 i18n, 1 Security, 1 Performance, 1 Business Impact, 1 Backend Contract, 1 Monorepo, 1 Tailwind, 1 UI Component Library |5051Usage: /protocol <name> <task>52```
Jagoda11