@ycodium-ai/plugin-team 0.2.3474 → 0.2.3484
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.
- package/README.md +13 -2
- package/assets/ui.js +17 -11
- package/dist/index.js +4134 -2379
- package/locales/en.json +81 -1
- package/locales/zh-CN.json +81 -1
- package/package.json +5 -3
package/README.md
CHANGED
|
@@ -30,12 +30,22 @@ while a goal is running gets a conversation of its own (an agent that has no goa
|
|
|
30
30
|
the next one); work already in a conversation's hands stays with it when the member later runs elsewhere. When
|
|
31
31
|
a member is removed, the work that has not reached it is taken back and the lead is told.
|
|
32
32
|
|
|
33
|
+
A new agent member, and one whose machine or model changed, first passes a short trial run: a small
|
|
34
|
+
conversation (or, for a remote agent, a message that wakes it on its own machine) that reads the project's
|
|
35
|
+
handbook and reports the release it read through the plugin's `team_trial_done` tool. Until then it is woken
|
|
36
|
+
for no work and cannot start any, and a goal cannot start with a lead that has not passed. A person can retry
|
|
37
|
+
a failed trial run or skip it from the Teams page; when skipping is the right call is in the
|
|
38
|
+
[user guide](../../docs/user/teams.md#when-to-skip-a-trial-run). Trial runs have been verified in real sessions with Claude Code only, on this machine and
|
|
39
|
+
on a remote seat; the release check was not exercised, and the other providers have not been verified. The
|
|
40
|
+
provider-by-provider table is in the [team plugin](../../docs/internals/team-plugin.md#trial-run) page.
|
|
41
|
+
|
|
33
42
|
Starting a goal also puts the goal on the board as a work item assigned to the lead, recorded
|
|
34
43
|
with this plugin as its author. The lead does no item itself, merging and pushing included; when
|
|
35
44
|
everything the goal waits on is finished, it checks the results and marks the goal item done,
|
|
36
45
|
and the goal bar shows that item's state.
|
|
37
46
|
|
|
38
|
-
Member conversations
|
|
47
|
+
Member conversations start without messages; each gets its first one when work is assigned to its member.
|
|
48
|
+
The project board shows up to 500 work items,
|
|
39
49
|
supports creation and assignment to the project's members, and moves cards between states
|
|
40
50
|
by dragging or using the card menu.
|
|
41
51
|
Open a card's details to read its description, follow dependencies, reply to comments, and see who changed it.
|
|
@@ -44,7 +54,8 @@ Mobile does not render the project workbench seat.
|
|
|
44
54
|
The plugin declares `work.read`, `members.read`, `work.writeAsPerson`, `communication.read` (to show
|
|
45
55
|
people's names in history), the `project.workbench.tab` UI seat, and
|
|
46
56
|
command dispatch permission for creating conversations, starting the lead's first turn, creating or
|
|
47
|
-
updating work items, posting comments,
|
|
57
|
+
updating work items, posting comments, adding, changing, removing and restoring project members, and
|
|
58
|
+
archiving and stopping the trial-run conversations it opened itself.
|
|
48
59
|
Work items, comments and members you change in the tab are recorded as yours, with this plugin shown as
|
|
49
60
|
the source.
|
|
50
61
|
|