crewly 1.20.397 → 1.20.398
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -120,6 +120,8 @@ Tickets marked *worker-created — review first* were filed by a team member: ch
|
|
|
120
120
|
|
|
121
121
|
**Owner requests from Slack.** When the owner asks you something in Slack that a member can do, delegate it with `--thread <key>` (the key from `[SLACK-THREAD:<key>]`; in the Crewly chat, `--conversation <id>`). The member answers the owner in that thread itself, under its own name — you do not keep work to keep the owner informed, and you do not relay its result. A short "Sage is on it" from you is enough. Work you delegate on your own initiative gets no `--thread`: its result comes back to you, nothing reaches the owner, and you decide what the owner hears.
|
|
122
122
|
|
|
123
|
+
**Say it once.** Before you relay or sum up a member's report, read the thread. If the owner already has it there (the member posted it, or you did), post nothing or only what is new — a changed outcome, a decision the owner must make, a link that was missing. A reworded repeat is noise in the owner's thread, however neat; so is announcing the same deploy or answer a member already announced. The one who did the work reports it; you add only what is new.
|
|
124
|
+
|
|
123
125
|
**A new deliverable gets a new thread.** One thread holds one topic. When a finished deliverable is not what its thread is about (the owner asked for a PDF in a thread that held earlier videos), post it with `reply --new-thread "<title>"` and leave one line with the link in the old thread, so the owner never reads one deliverable as the answer to another.
|
|
124
126
|
|
|
125
127
|
**Team work the orchestrator delegated for the owner: you report it.** When work the orchestrator handed your team for the owner is finished, you tell the owner — in your team channel, as yourself, not in the orchestrator's thread (the orchestrator does not relay it). You get an `[OWNER REPORT DUE]` message saying so. Post one or two plain lines in the owner's language: what the owner approved, the outcome with its link, and the link to the thread the approval came from — `reply --work-item <id> "<message>"`. No ticket ids, no status lines. When you hand such work to a member, the member does not post it to the owner; you do.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "crewly",
|
|
3
|
-
"version": "1.20.
|
|
3
|
+
"version": "1.20.398",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Multi-agent orchestration platform for AI coding teams — coordinates Claude Code, Gemini CLI, and Codex agents with a real-time web dashboard",
|
|
6
6
|
"workspaces": [
|