Wire Linear and Slack specialists and prompt routing.

surfsense_backend/app/agents/new_chat/prompts/base/tool_routing_private.md

@@ -5,12 +5,19 @@ say "I don't see it in the knowledge base" or ask the user if they want you to c
 Ignore any knowledge base results for these services.
 
 When to use which tool:
-- Linear (issues) → list_issues, get_issue, save_issue (create/update)
+- Linear (issues, teams, users, projects when MCP exposes them) → hosted Linear MCP read tools (e.g. `list_issues`, `get_issue`, `list_teams`, `list_users`, …) and `save_issue` for create/update; native SurfSense Linear issue tools when present. For **multi-step Linear-only** work (several reads, structured evidence), delegate with the `task` tool to subagent **`linear_specialist`** instead of mixing unrelated tools.
 - ClickUp (tasks) → clickup_search, clickup_get_task
 - Jira (issues) → getAccessibleAtlassianResources (cloudId discovery), getVisibleJiraProjects (project discovery), getJiraProjectIssueTypesMetadata (issue type discovery), searchJiraIssuesUsingJql, createJiraIssue, editJiraIssue
-- Slack (messages, channels) → slack_search_channels, slack_read_channel, slack_read_thread
+- Slack (messages, channels) → `slack_search_channels`, `slack_read_channel`, `slack_read_thread`, and other `slack_*` tools when connected. For **multi-step Slack-only** work, delegate with `task` to **`slack_specialist`**.
 - Airtable (bases, tables, records) → list_bases, list_tables_for_base, list_records_for_table
 - Knowledge base content (Notion, GitHub, files, notes) → automatically searched
 - Real-time public web data → call web_search
 - Reading a specific webpage → call scrape_webpage
+
+**`task` subagents (when to delegate):**
+- **`linear_specialist`** — Linear-only investigations and tool use.
+- **`slack_specialist`** — Slack-only investigations and tool use.
+- **`connector_negotiator`** — **Cross-connector** chains (e.g. data from Slack then action in Linear).
+- **`explore`** — Read-only KB + web research with citations.
+- **`report_writer`** — Single `generate_report` deliverable.
 </tool_routing>

surfsense_backend/app/agents/new_chat/prompts/base/tool_routing_team.md

@@ -5,12 +5,19 @@ say "I don't see it in the knowledge base" or ask if they want you to check.
 Ignore any knowledge base results for these services.
 
 When to use which tool:
-- Linear (issues) → list_issues, get_issue, save_issue (create/update)
+- Linear (issues, teams, users, projects when MCP exposes them) → hosted Linear MCP read tools (e.g. `list_issues`, `get_issue`, `list_teams`, `list_users`, …) and `save_issue` for create/update; native SurfSense Linear issue tools when present. For **multi-step Linear-only** work (several reads, structured evidence), delegate with the `task` tool to subagent **`linear_specialist`** instead of mixing unrelated tools.
 - ClickUp (tasks) → clickup_search, clickup_get_task
 - Jira (issues) → getAccessibleAtlassianResources (cloudId discovery), getVisibleJiraProjects (project discovery), getJiraProjectIssueTypesMetadata (issue type discovery), searchJiraIssuesUsingJql, createJiraIssue, editJiraIssue
-- Slack (messages, channels) → slack_search_channels, slack_read_channel, slack_read_thread
+- Slack (messages, channels) → `slack_search_channels`, `slack_read_channel`, `slack_read_thread`, and other `slack_*` tools when connected. For **multi-step Slack-only** work, delegate with `task` to **`slack_specialist`**.
 - Airtable (bases, tables, records) → list_bases, list_tables_for_base, list_records_for_table
 - Knowledge base content (Notion, GitHub, files, notes) → automatically searched
 - Real-time public web data → call web_search
 - Reading a specific webpage → call scrape_webpage
+
+**`task` subagents (when to delegate):**
+- **`linear_specialist`** — Linear-only investigations and tool use.
+- **`slack_specialist`** — Slack-only investigations and tool use.
+- **`connector_negotiator`** — **Cross-connector** chains (e.g. data from Slack then action in Linear).
+- **`explore`** — Read-only KB + web research with citations.
+- **`report_writer`** — Single `generate_report` deliverable.
 </tool_routing>

surfsense_backend/app/agents/new_chat/prompts/routing/linear.md

@@ -1 +1,3 @@
-
+<linear_routing>
+**Linear:** Prefer the `task` tool with subagent **`linear_specialist`** when the user’s request is **only about Linear** and may need several tool calls (list issues, inspect one issue, teams, users, statuses, comments, documents). Use **`connector_negotiator`** when Linear is one hop in a **multi-connector** workflow. Call Linear MCP tools directly from the parent when a **single** quick call is enough.
+</linear_routing>

surfsense_backend/app/agents/new_chat/prompts/routing/slack.md

@@ -1 +1,3 @@
-
+<slack_routing>
+**Slack:** Prefer `task` with **`slack_specialist`** for **Slack-only** multi-step work (channels, threads, reads, writes that need approval in the specialist). Use **`connector_negotiator`** when Slack feeds another connector in one chain. Use direct `slack_*` tools from the parent for a **single** quick read or write when appropriate.
+</slack_routing>