specialistslisted

# Specialist Management The user wants to manage persistent specialist agents. ## Protocol 1. **Parse arguments**: `$ARGUMENTS` - If empty or "list": Show all specialists in table format - If starts with "view": Show full content of named specialist - If starts with "remove": Delete named specialist with confirmation - If starts with "edit": Allow user to modify named specialist 2. **Registry file**: `.orchestray/specialists/registry.json`. If the directory or file does not exist, report: "No specialist registry found. Orchestray ships built-in specialist templates (at `<plugin-root>/specialists/`) and creates project-local ones at `.orchestray/specialists/` when dynamic agents succeed. You can also place custom .md files directly in `.orchestray/specialists/`." ### List Operation Read `.orchestray/specialists/registry.json` and parse the `specialists` array. Display a table: ``` | Name | Source | Uses | Last Used | Description | |------|--------|------|-----------|-------------| | {name} | {source} | {times_used} | {last_used} | {description} | ``` Below the table, show: "{N} specialist(s) registered." Then show usage hints: - `view {name}` -- Show full specialist definition - `remove {name}` -- Remove a specialist - `edit {name}` -- Edit a specialist If the `specialists` array is empty, show: "No project-local specialists registered yet. Note: Orchestray ships built-in specialist templates (translator, ui-ux-designer) at `<plugin-root>/specialists/` —