multica-squads

Name: multica-squads
Author: multica-ai

10installs5.2kforks

How to install multica-squads?

multica-ai/multica/multica-squads

$npx -y skills add multica-ai/multica --skill multica-squads

Installs into the current project.

Summary

Use when creating, inspecting, updating, assigning, mentioning, or debugging Multica squads. Explains what squads are, squad/member fields, CLI commands, leader routing, issue assignment, comments, mentions, autopilot behavior, leader briefing, side effects, and product-gap handl

Files · 1

View on GitHub

SKILL.md

1	# Multica Squads
2
3	## Quick start
4
5	If debugging why a squad did or did not run, inspect first:
6
7	```bash
8	multica issue get <issue-id> --output json
9	multica squad get <squad-id> --output json
10	multica squad member list <squad-id> --output json
11	multica issue comment list <issue-id> --recent 10 --output json
12	```
13
14	If the command shape is unclear, check help instead of guessing:
15
16	```bash
17	multica squad --help
18	multica squad member --help
19	multica issue update --help
20	multica issue comment add --help
21	```
22
23	Do not assign, comment, mention, update, delete, or record squad activity just
24	to test. These can mutate workspace state or trigger agent runs.
25
26	## Core model
27
28	A Multica squad is a workspace routing and coordination object.
29
30	A squad is not an agent. It does not run work by itself. Current behavior:
31	squad-routed work runs through the squad's `leader_id` agent.
32
33	Important consequences:
34
35	- assigning an issue to a squad routes to the leader;
36	- mentioning a squad routes to the leader;
37	- squad-assigned autopilot resolves to the leader;
38	- squad members are not automatically fanned out;
39	- squad `instructions` are leader briefing content, not member prompts.
40
41	## CLI
42
43	Squad commands:
44
45	```bash
46	multica squad list --output json
47	multica squad get <squad-id> --output json
48	multica squad create --name <name> --leader <agent-name-or-id> --output json
49	multica squad update <squad-id> --instructions "<leader coordination policy>" --output json
50	multica squad delete <squad-id>
51	```
52
53	Member commands:
54
55	```bash
56	multica squad member list <squad-id> --output json
57	multica squad member add <squad-id> --member-id <id> --type agent\|member --role <role> --output json
58	multica squad member remove <squad-id> --member-id <id> --type agent\|member
59	multica squad member set-role <squad-id> --member-id <id> --member-type agent\|member --role <role> --output json
60	```
61
62	Squad leader evaluation command:
63
64	```bash
65	multica squad activity <issue-id> action\|no_action\|failed --reason "<why>" --output json
66	```
67
68	`activity` is a write: it records the leader's evaluation decision on an issue.
69	Use it only when acting as the squad leader after evaluating a trigger.
70
71	Issue/comment commands often needed with squads:
72
73	```bash
74	multica issue get <issue-id> --output json
75	multica issue update <issue-id> --help
76	multica issue comment list <issue-id> --output json
77	multica issue comment add <issue-id> --help
78	```
79
80	Prefer `--output json` for reads. Use `--help` before writes.
81
82	## Squad fields
83
84	- `id` — squad UUID.
85	- `workspace_id` — workspace the squad belongs to.
86	- `name` — display name; unique per workspace.
87	- `description` — human-facing metadata/display text. Do not assume runtime
88	prompt impact unless source proves a consumer.
89	- `instructions` — squad-level instructions added to the squad leader briefing.
90	They are not directly injected into every squad member.
91	- `avatar_url` — optional squad avatar URL.
92	- `leader_id` — agent ID of the squad leader; the runtime target for
93	squad-routed work.
94	- `creator_id` — creator of the squad.
95	- `archived_at` / `archived_by` — archive metadata. Archived squads are rejected
96	by assignment/autopilot routing paths.
97	- `member_count` — list response count of squad members.
98	- `member_preview` — list response preview of squad members.
99
100	Use `instructions` for leader-facing coordination policy: squad responsibility,
101	delegation expectations, when to ask humans, and review/handoff rules. Do not
102	write it as if every member automatically receives it.
103
104	## Squad member fields
105
106	- `member_type` — `agent` or `member`.
107	- `member_id` — ID of the agent or workspace member.
108	- `role` — roster role label. Current behavior: non-empty `role` appears in the
109	leader briefing roster. Do not assume it creates scheduling, permissions, or
110	routing behavior.
111
112	## Creation and leader membership
113
114	Creating a squad requires `leader_id`. The leader must be a workspace agent.
115	Create/update does not reject an archived leader: the lookup only checks the
116	agent exists in the workspace. An archived leader fails closed later, at
117	routing/dispatch — assignment, autopilot admission, and the comment/mention
118	readiness gate all reject an archived leader before any task is enqueued.
119
120	On create, the backend attempts to add the leader as a squad member with role
121	`leader`. When updating `leader_id`, if the new leader is not already a member,
122	the backend adds the new leader as a squad member with role `leader`.
123
124	## Leader briefing
125
126	For squad leader tasks, Multica appends a squad leader briefing to the leader
127	agent instructions. The briefing includes:
128
129	- Squad Operating Protocol;
130	- Squad Roster;
131	- Squad Instructions, only wh

People who liked this also viewed

6 picks

Type

multica-squads

10installs5.2kforks

View on GitHub

How to install multica-squads?

multica-ai/multica/multica-squads

$npx -y skills add multica-ai/multica --skill multica-squads

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Multica Squads
2
3	## Quick start
4
5	If debugging why a squad did or did not run, inspect first:
6
7	```bash
8	multica issue get <issue-id> --output json
9	multica squad get <squad-id> --output json
10	multica squad member list <squad-id> --output json
11	multica issue comment list <issue-id> --recent 10 --output json
12	```
13
14	If the command shape is unclear, check help instead of guessing:
15
16	```bash
17	multica squad --help
18	multica squad member --help
19	multica issue update --help
20	multica issue comment add --help
21	```
22
23	Do not assign, comment, mention, update, delete, or record squad activity just
24	to test. These can mutate workspace state or trigger agent runs.
25
26	## Core model
27
28	A Multica squad is a workspace routing and coordination object.
29
30	A squad is not an agent. It does not run work by itself. Current behavior:
31	squad-routed work runs through the squad's `leader_id` agent.
32
33	Important consequences:
34
35	- assigning an issue to a squad routes to the leader;
36	- mentioning a squad routes to the leader;
37	- squad-assigned autopilot resolves to the leader;
38	- squad members are not automatically fanned out;
39	- squad `instructions` are leader briefing content, not member prompts.
40
41	## CLI
42
43	Squad commands:
44
45	```bash
46	multica squad list --output json
47	multica squad get <squad-id> --output json
48	multica squad create --name <name> --leader <agent-name-or-id> --output json
49	multica squad update <squad-id> --instructions "<leader coordination policy>" --output json
50	multica squad delete <squad-id>
51	```
52
53	Member commands:
54
55	```bash
56	multica squad member list <squad-id> --output json
57	multica squad member add <squad-id> --member-id <id> --type agent\|member --role <role> --output json
58	multica squad member remove <squad-id> --member-id <id> --type agent\|member
59	multica squad member set-role <squad-id> --member-id <id> --member-type agent\|member --role <role> --output json
60	```
61
62	Squad leader evaluation command:
63
64	```bash
65	multica squad activity <issue-id> action\|no_action\|failed --reason "<why>" --output json
66	```
67
68	`activity` is a write: it records the leader's evaluation decision on an issue.
69	Use it only when acting as the squad leader after evaluating a trigger.
70
71	Issue/comment commands often needed with squads:
72
73	```bash
74	multica issue get <issue-id> --output json
75	multica issue update <issue-id> --help
76	multica issue comment list <issue-id> --output json
77	multica issue comment add <issue-id> --help
78	```
79
80	Prefer `--output json` for reads. Use `--help` before writes.
81
82	## Squad fields
83
84	- `id` — squad UUID.
85	- `workspace_id` — workspace the squad belongs to.
86	- `name` — display name; unique per workspace.
87	- `description` — human-facing metadata/display text. Do not assume runtime
88	prompt impact unless source proves a consumer.
89	- `instructions` — squad-level instructions added to the squad leader briefing.
90	They are not directly injected into every squad member.
91	- `avatar_url` — optional squad avatar URL.
92	- `leader_id` — agent ID of the squad leader; the runtime target for
93	squad-routed work.
94	- `creator_id` — creator of the squad.
95	- `archived_at` / `archived_by` — archive metadata. Archived squads are rejected
96	by assignment/autopilot routing paths.
97	- `member_count` — list response count of squad members.
98	- `member_preview` — list response preview of squad members.
99
100	Use `instructions` for leader-facing coordination policy: squad responsibility,
101	delegation expectations, when to ask humans, and review/handoff rules. Do not
102	write it as if every member automatically receives it.
103
104	## Squad member fields
105
106	- `member_type` — `agent` or `member`.
107	- `member_id` — ID of the agent or workspace member.
108	- `role` — roster role label. Current behavior: non-empty `role` appears in the
109	leader briefing roster. Do not assume it creates scheduling, permissions, or
110	routing behavior.
111
112	## Creation and leader membership
113
114	Creating a squad requires `leader_id`. The leader must be a workspace agent.
115	Create/update does not reject an archived leader: the lookup only checks the
116	agent exists in the workspace. An archived leader fails closed later, at
117	routing/dispatch — assignment, autopilot admission, and the comment/mention
118	readiness gate all reject an archived leader before any task is enqueued.
119
120	On create, the backend attempts to add the leader as a squad member with role
121	`leader`. When updating `leader_id`, if the new leader is not already a member,
122	the backend adds the new leader as a squad member with role `leader`.
123
124	## Leader briefing
125
126	For squad leader tasks, Multica appends a squad leader briefing to the leader
127	agent instructions. The briefing includes:
128
129	- Squad Operating Protocol;
130	- Squad Roster;
131	- Squad Instructions, only wh

People who liked this also viewed

6 picks

Type