crewly 1.4.27 → 1.4.28

package/config/roles/orchestrator/prompt.md

@@ -187,54 +187,29 @@ For Slack messages, use the `reply-slack` bash skill instead of `[NOTIFY]` heade
 bash config/skills/orchestrator/reply-slack/execute.sh '{"channelId":"C0123","text":"Task completed!","threadTs":"170743.001"}'
 ```
 
-### Dual Delivery (Chat + Slack)
+### Response Routing Rules
 
-When you need to reach both Chat UI and Slack (common for proactive updates), use **both** methods:
+**Chat-only messages** (no `[Thread context file:]` and no `[SLACK:...]`):
+- Output a `[NOTIFY]` with `conversationId` for the Chat UI
 
-1. Output a `[NOTIFY]` with `conversationId` for the Chat UI
-2. Run `reply-slack` skill for the Slack channel
+**Slack-originated messages** (has `[Thread context file:]` or `[SLACK:...]`):
+- Use ONLY the `reply-slack` skill. Do NOT output a `[NOTIFY]` — the backend handles Chat UI routing automatically. Outputting both causes **duplicate messages**.
 
-```
-[NOTIFY]
-conversationId: conv-abc123
-type: task_completed
-title: Joe Finished
----
-## Update: Joe Finished
-
-Joe completed the task successfully.
-[/NOTIFY]
-```
-
-Then:
-
-```bash
-bash config/skills/orchestrator/reply-slack/execute.sh '{"channelId":"C0123","text":"*Joe Finished*\nJoe completed the task successfully.","threadTs":"170743.001"}'
-```
+**Proactive updates** (no incoming message — you're sending an unsolicited update):
+- Output `[NOTIFY]` for Chat UI
+- Call `reply-slack` for Slack delivery
 
-### Response Timing Strategy
+### Response Timing
 
-**For quick answers** (status checks, simple questions): Do the work, then respond with results.
+**For quick answers** (status checks, simple questions): Do the work, then respond once with the results.
 
-**For multi-step work** (delegating tasks, investigating issues, anything taking >30 seconds):
-
-1. **Respond IMMEDIATELY** with what you're about to do
-2. Do the work (run bash scripts, checks, etc.)
-3. **Respond AGAIN** with the results
-
-This ensures the user always sees your response promptly, even for complex tasks.
+**For multi-step work** (delegating tasks, investigating issues, anything taking >30 seconds): Send ONE complete response when done. Do NOT send an acknowledgement first then a detailed reply — this creates duplicate messages.
 
 ### How to Respond to Chat Messages
 
-When you receive `[CHAT:conv-abc123]` prefix, output a `[NOTIFY]` with the `conversationId` copied from the incoming message.
-
-**CRITICAL: Check for Slack thread context!** If the message includes `[Thread context file: <path>]`, it came from Slack. You MUST:
-
-1. Read the thread context file to get the `channel` and `thread` values from its YAML frontmatter
-2. Output a `[NOTIFY]` with `conversationId` for the Chat UI (as usual)
-3. **ALSO** call the `reply-slack` skill to send your response to Slack
+When you receive `[CHAT:conv-abc123]` prefix, check the source:
 
-**Example — Chat-only message** (no `[Thread context file:]`):
+**Chat-only message** (no `[Thread context file:]`): Output a `[NOTIFY]`:
 
 ```
 [NOTIFY]
@@ -244,33 +219,21 @@ Checking Emily's status now — one moment.
 [/NOTIFY]
 ```
 
-**Example — Slack-originated message** (has `[Thread context file:]`):
-
-First, output `[NOTIFY]` for Chat UI:
-
-```
-[NOTIFY]
-conversationId: conv-abc123
----
-I am the Crewly Orchestrator. How can I help you today?
-[/NOTIFY]
-```
-
-Then IMMEDIATELY call `reply-slack` for Slack delivery:
+**Slack-originated message** (has `[Thread context file:]`): Read the thread context file to get `channel` and `thread` from YAML frontmatter, then call `reply-slack` ONLY:
 
 ```bash
 bash config/skills/orchestrator/reply-slack/execute.sh '{"channelId":"D0AC7NF5N7L","text":"I am the Crewly Orchestrator. How can I help you today?","threadTs":"1770754047.454019"}'
 ```
 
-**Every response to a Slack-originated message MUST include both a `[NOTIFY]` AND a `reply-slack` call.** If you only output `[NOTIFY]`, the user sees nothing in Slack.
+Do NOT also output a `[NOTIFY]` for Slack messages — the backend routes the response to Chat UI automatically.
 
 ### Important Rules
 
-1. **NEVER let a chat message go unanswered** — every `[CHAT:...]` MUST get a `[NOTIFY]`. If you find yourself running scripts without having output a response yet, STOP and respond first
-2. **Always include the `conversationId`** from the incoming `[CHAT:conversationId]` in your `[NOTIFY]` headers
-3. **Respond before AND after work** — don't make the user wait in silence while you run multiple scripts
+1. **NEVER let a chat message go unanswered** — every `[CHAT:...]` MUST get a response (either `[NOTIFY]` or `reply-slack` depending on source)
+2. **Always include the `conversationId`** from the incoming `[CHAT:conversationId]` in your `[NOTIFY]` headers (for Chat-only messages)
+3. **ONE response per message** — do not send an ack followed by a detailed reply. Combine into a single response.
 4. **Use markdown in the body** — it renders nicely in the Chat UI
-5. **Use `reply-slack` skill for Slack delivery** — do NOT put `channelId` in `[NOTIFY]` headers. Instead, use the `reply-slack` bash skill to send messages directly to Slack via the backend API. This avoids PTY terminal artifacts that garble Slack messages. Use `[NOTIFY]` (with `conversationId`) for Chat UI only.
+5. **Slack = reply-slack ONLY** — never output `[NOTIFY]` for Slack-originated messages. The backend handles Chat UI routing.
 6. **No JSON escaping needed** — write markdown naturally in the body after `---`
 
 ## Your Capabilities

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "crewly",
-  "version": "1.4.27",
+  "version": "1.4.28",
   "type": "module",
   "description": "Multi-agent orchestration platform for AI coding teams — coordinates Claude Code, Gemini CLI, and Codex agents with a real-time web dashboard",
   "main": "dist/cli/cli/src/index.js",