@ycodium-ai/plugin-team 0.2.3433 → 0.2.3474

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 CHANGED
@@ -1,39 +1,52 @@
1
1
  # @ycodium-ai/plugin-team
2
2
 
3
- Save a project's team members, choose a lead, and give that lead a goal. The **Teams**
4
- project workbench tab on Web and Desktop opens a conversation for each member and sends the lead
3
+ Manage a project's team members, choose a lead, and give that lead a goal. The **Teams**
4
+ project workbench tab on Web and Desktop opens a conversation for each agent member and sends the lead
5
5
  a brief for splitting and assigning the work.
6
6
 
7
7
  This plugin is bundled with Ycodium as `core.team` and is enabled by default.
8
8
  It has no separate installation step in a bundled checkout. Enabling the plugin exposes the tab;
9
- disabling it removes the tab and commands. Saved roster and goal facts stay in the host event log,
9
+ disabling it removes the tab and commands. The lead and goal facts stay in the host event log,
10
10
  and enabling it again rebuilds their state. Existing conversations remain in the conversation list.
11
11
 
12
- Each project has one roster of 1–8 members. Names must be distinct after trimming surrounding
13
- spaces and ignoring capitalization. One member must be the lead. Concurrent edits use revisions;
14
- the editor reloads the roster when another writer has saved a newer revision.
12
+ A project's team is its active agent members, 1–8 of them, kept in the host's project members: the
13
+ tab adds, edits, removes and restores them as you, and records you as the author. People can be
14
+ members too but take no part in a goal. Names must be distinct after trimming surrounding spaces and
15
+ ignoring capitalization. One local agent member must be the lead; the plugin stores only that choice.
16
+ A roster saved before members lived in the host keeps working until you import it from the tab. On
17
+ mobile the plugin's page lists the members read-only. The lead of the current goal can also add, change,
18
+ remove and restore agent members with the `team_create_member`, `team_update_member`,
19
+ `team_remove_member` and `team_restore_member` tools; the plugin writes those changes and keeps who asked
20
+ in its own facts.
15
21
 
16
22
  Keep the project's board and project memory switches on so the lead can create work items and
17
- assign them to member conversations. Starting another goal asks for confirmation; the previous
23
+ assign them to members. Starting another goal asks for confirmation; the previous
18
24
  goal's conversations keep running. If starting fails midway, Retry completes the same request
19
25
  without creating duplicate conversations or sending the lead another first turn.
20
26
 
27
+ Work can be assigned to a member as well as to a conversation. The assignment wakes the conversation that runs
28
+ for that member in the current goal, and the member starts it by moving it into progress. A member who joins
29
+ while a goal is running gets a conversation of its own (an agent that has no goal to join waits for
30
+ the next one); work already in a conversation's hands stays with it when the member later runs elsewhere. When
31
+ a member is removed, the work that has not reached it is taken back and the lead is told.
32
+
21
33
  Starting a goal also puts the goal on the board as a work item assigned to the lead, recorded
22
34
  with this plugin as its author. The lead does no item itself, merging and pushing included; when
23
35
  everything the goal waits on is finished, it checks the results and marks the goal item done,
24
36
  and the goal bar shows that item's state.
25
37
 
26
38
  Member conversations initially have no messages. The project board shows up to 500 work items,
27
- supports creation and assignment to the current goal's members, and moves cards between states
39
+ supports creation and assignment to the project's members, and moves cards between states
28
40
  by dragging or using the card menu.
29
41
  Open a card's details to read its description, follow dependencies, reply to comments, and see who changed it.
30
42
  It does not provide sorting or filters.
31
43
  Mobile does not render the project workbench seat.
32
- The plugin declares `work.read`, `work.writeAsPerson`, `communication.read` (to show people's names
33
- in history), the `project.workbench.tab` UI seat, and
34
- command dispatch permission for creating conversations, starting the lead's first turn, and
35
- creating or updating work items and posting comments. Work items and comments you change in the
36
- tab are recorded as yours, with this plugin shown as the source.
44
+ The plugin declares `work.read`, `members.read`, `work.writeAsPerson`, `communication.read` (to show
45
+ people's names in history), the `project.workbench.tab` UI seat, and
46
+ command dispatch permission for creating conversations, starting the lead's first turn, creating or
47
+ updating work items, posting comments, and adding, changing, removing and restoring project members.
48
+ Work items, comments and members you change in the tab are recorded as yours, with this plugin shown as
49
+ the source.
37
50
 
38
51
  Implementation and command shapes: [team plugin](../../docs/internals/team-plugin.md).
39
52