squadrant 0.17.1 → 0.18.0
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/dist/index.js +585 -324
- package/dist/index.js.map +1 -1
- package/dist/squadrantd.js +52 -5
- package/dist/squadrantd.js.map +1 -1
- package/package.json +1 -1
- package/plugin/skills/captain-ops/SKILL.md +1 -1
- package/plugin/skills/handback/SKILL.md +8 -0
- package/plugin/skills/takeover/SKILL.md +11 -0
- package/templates/captain.claude.md +1 -0
- package/templates/captain.generic.md +1 -0
package/package.json
CHANGED
|
@@ -194,7 +194,7 @@ To change the effort dial: `squadrant effort <max|balance|low>` or use the `squa
|
|
|
194
194
|
- **Close crews you're done with** (`squadrant crew close ...`) so they don't accumulate.
|
|
195
195
|
- Crews run in **isolated worktrees by default** (parallel-safe, branch per crew). Pass `--shared` only for tiny/one-off tasks that don't need branch isolation. Never hand-run `git worktree add` — `squadrant crew spawn` handles it.
|
|
196
196
|
- Do NOT edit source code yourself — always delegate to crew.
|
|
197
|
-
- Respect `maxCrew` — don't exceed the configured concurrent crew count.
|
|
197
|
+
- Respect `maxCrew` — don't exceed the configured concurrent crew count. Held crews do not count toward the limit, and at the limit you must ask the operator rather than choosing a crew to close.
|
|
198
198
|
- **For complex multi-step tasks** (3+ steps, multiple files), tell the crew to use GSD inside the task prompt: *"This is a complex task. Use `/gsd:plan-phase` and `/gsd:execute-phase` for wave-based execution with fresh context per step."*
|
|
199
199
|
- **For simple tasks**, don't mention GSD — the crew will handle it directly.
|
|
200
200
|
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
# /handback
|
|
2
|
+
|
|
3
|
+
Runs when the operator is finished driving this tab and wants to return control to the captain.
|
|
4
|
+
|
|
5
|
+
1. First, you MUST run this command to clear the takeover in the control plane:
|
|
6
|
+
`squadrant crew handback --task-id "$SQUADRANT_CREW_TASK_ID"`
|
|
7
|
+
|
|
8
|
+
2. Acknowledge to the user: you have returned control to the captain. You are no longer in operator mode, and the normal completion protocol (running `squadrant crew signal done` when finished) applies again.
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
# /takeover
|
|
2
|
+
|
|
3
|
+
Runs when the operator wants to take direct control of this crew tab.
|
|
4
|
+
|
|
5
|
+
1. First, you MUST run this command to record the takeover in the control plane:
|
|
6
|
+
`squadrant crew takeover --task-id "$SQUADRANT_CREW_TASK_ID"`
|
|
7
|
+
|
|
8
|
+
2. Acknowledge to the user: you now work directly for the operator, not the captain.
|
|
9
|
+
**Do not run `squadrant crew signal done`** when you finish what the operator asked — wait for `/handback`.
|
|
10
|
+
|
|
11
|
+
You are now in operator mode.
|
|
@@ -37,6 +37,7 @@ You are a **project captain** for Squadrant. You lead ONE project. You are a **c
|
|
|
37
37
|
squadrant crew read <project> <name> # read its screen
|
|
38
38
|
squadrant crew close <project> <name> # shutdown when done
|
|
39
39
|
```
|
|
40
|
+
**Operator Takeover:** A crew under operator takeover is off-limits — no `send`, no `close`, and its lifecycle signals are not yours to act on. If you are at your crew limit, **ask the operator**; never pick a held crew to close. `--force` exists only for when the operator explicitly tells you to use it.
|
|
40
41
|
3. **Record learnings** when something unexpected happens or a pattern emerges (`squadrant:captain-ops` shows the script).
|
|
41
42
|
4. **Compact recovery** — if you feel disoriented after `/compact`, re-read your handoff (`{spokeVault}/handoffs/`) to restore work context. Role itself survives compact via `--append-system-prompt-file`.
|
|
42
43
|
|
|
@@ -16,6 +16,7 @@ You are a project captain coordinating work via cmux workspaces. You are a coord
|
|
|
16
16
|
squadrant crew close <project> <name> # shutdown when done
|
|
17
17
|
squadrant crew list <project> # all live crews
|
|
18
18
|
```
|
|
19
|
+
**Operator Takeover:** A crew under operator takeover is off-limits — no `send`, no `close`, and its lifecycle signals are not yours to act on. If you are at your crew limit, **ask the operator**; never pick a held crew to close. `--force` exists only for when the operator explicitly tells you to use it.
|
|
19
20
|
4. Communicate with the project's captain workspace via:
|
|
20
21
|
```bash
|
|
21
22
|
squadrant runtime send <project> "<message>"
|