@ours.network/fleet-claude-code 0.1.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "ours-fleet",
+  "description": "Spawn and oversee ours-fleet agents from inside Claude Code",
+  "version": "0.1.0",
+  "author": { "name": "ours.network contributors", "url": "https://ours.network" }
+}

package/package.json

@@ -0,0 +1,17 @@
+{
+  "name": "@ours.network/fleet-claude-code",
+  "version": "0.1.0",
+  "description": "Claude Code plugin for ours-fleet — spawn and oversee fleet agents from inside a session. Bundles the spawn-ours-agent and oversee-agents skills; the ours-fleet CLI (@ours.network/fleet) does the actual work.",
+  "license": "FSL-1.1-Apache-2.0",
+  "author": "ours.network contributors",
+  "homepage": "https://github.com/adapt-toolkit/ours-fleet/tree/main/integrations/claude-code#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/adapt-toolkit/ours-fleet.git",
+    "directory": "integrations/claude-code"
+  },
+  "keywords": ["claude", "claude-code", "plugin", "fleet", "agents", "tmux", "spawn", "oversight", "ours"],
+  "files": [".claude-plugin", "skills"],
+  "publishConfig": { "access": "public" },
+  "engines": { "node": ">=20" }
+}

package/skills/oversee-agents/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: oversee-agents
+description: Keep an eye on ours-fleet agents you spawned or were assigned - periodically peek into their tmux consoles, unstick them (answer prompts, approve dialogs, nudge) via ours-fleet send, escalate only when unsure. Use when the user or your persona/briefing says "keep an eye on X", "oversee agents", "watch agents", or right after spawning an agent.
+---
+
+# Oversee ours-fleet agents
+
+Your wards are subagents — you own their liveness. The core gives you two
+primitives; the judgment is yours.
+
+```bash
+ours-fleet peek <Name> [lines]        # console snapshot (default 40 lines)
+ours-fleet send <Name> "<text>"       # type into its console (+ Enter)
+ours-fleet send <Name> --key <K>      # raw key: Escape, Up, C-c, "1", ...
+```
+
+## 1. Determine your assignment
+
+Wards and intervals come from any of:
+- an explicit request ("keep an eye on Alice and Bob every 5 minutes"),
+- your briefing's **## Oversight assignments** section,
+- your persona text,
+- an agent you just spawned (default interval 5m).
+
+## 2. Arm the loop
+
+Schedule a repeating check every N minutes using your harness's mechanism
+(scheduled wake-ups or a persistent background monitor). One tick = check every
+ward once. Keep the loop armed across restarts — re-arm it right after re-binding
+your identity.
+
+## 3. Each tick: peek and judge
+
+Run `ours-fleet peek <Name>` per ward and classify the console:
+
+| Console shows | Action |
+|---|---|
+| Permission prompt, trust dialog, numbered menu ("1. Yes…") | Answer it directly: `ours-fleet send <Name> --key 1` (or the right key/text). Prefer the safe affirmative that unblocks the task the agent was assigned. |
+| A question the agent asked its (absent) user | Answer with what you know of the mission: `ours-fleet send <Name> "<answer>"`. |
+| Crashed to a shell prompt / error text | Investigate (`ours-fleet logs <Name>`); for permanent roles `ours-fleet restart <Name>`; report to the owner. |
+| Idle with work still assigned | Nudge: `ours-fleet send <Name> "Status? Continue with <task> or declare BLOCKED."` |
+| Actively working / healthy | Nothing. Do not interrupt. |
+
+## 4. Escalate when unsure
+
+If the resolution would make a decision that is not yours (spending, deleting,
+publishing, changing scope), do NOT press through it — message the owner or
+coordinator over ours messaging (`send_message`) with the pane snapshot and your
+recommendation.
+
+## 5. Log
+
+Append notable interventions (ward, what was stuck, what you did) to your
+WORKLOG so the history survives restarts.

package/skills/spawn-ours-agent/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: spawn-ours-agent
+description: Spawn a new ours-fleet agent (permanent fleet role or temporary background agent) from inside a session. Use when the user says "spawn ours agent", "spawn an agent", "create a fleet agent", "start a background agent", or asks for a new subagent that should live in its own tmux session.
+---
+
+# Spawn an ours-fleet agent
+
+You are about to create a new long-lived agent in its own tmux session, managed by
+`ours-fleet`. Follow these steps in order.
+
+## 1. Temporary or permanent?
+
+Ask the requester (skip only if they already said):
+
+- **Permanent** — written to `~/fleet.d/<Name>.yaml`, supervised (auto-restart,
+  survives reboot). For roles that should stay.
+- **Temporary** — plain tmux, auto-cleaned when it exits, gone on reboot. For
+  one-off background work. Killed by you or the coordinator when done.
+
+## 2. Pick a name
+
+`<Name>` must match `[A-Za-z0-9_-]+` (it becomes the tmux + service name). Check it
+is free: `ours-fleet config` must not list it and `ours-fleet ls` must not show it.
+
+## 3. Co-draft bio and persona
+
+Draft WITH the requester, iterating until they approve:
+
+- **Bio** — the public card peers and coordinators see (1–3 sentences: who this
+  agent is, what to ask it for).
+- **Persona** — the local operating contract (boundaries, quality bar, how it
+  works, when it escalates).
+
+Write them to temp files to avoid shell-quoting problems:
+
+```bash
+cat > /tmp/spawn-bio.md <<'EOF'
+<approved bio>
+EOF
+cat > /tmp/spawn-persona.md <<'EOF'
+<approved persona>
+EOF
+```
+
+## 4. Spawn
+
+Permanent (announce it to yourself if you are its coordinator):
+
+```bash
+ours-fleet spawn <Name> \
+  --mission "<one-line mission>" \
+  --bio-file /tmp/spawn-bio.md --persona-file /tmp/spawn-persona.md \
+  [--harness claude-code] [--cwd <dir>] [--coordinator <YourRoleName>]
+```
+
+Temporary:
+
+```bash
+ours-fleet spawn --temp <Name> \
+  --mission "<one-line mission>" \
+  --bio-file /tmp/spawn-bio.md --persona-file /tmp/spawn-persona.md
+```
+
+## 5. Verify
+
+```bash
+ours-fleet peek <Name> 30     # console snapshot — it should be booting its briefing
+ours-fleet status <Name>      # permanent roles: unit state
+```
+
+## 6. Arm oversight
+
+The spawner babysits its subagent. Ask the requester for a check interval
+(default **5m**), then follow the **oversee-agents** skill for `<Name>` at that
+interval. If you set `--coordinator <YourRoleName>`, the new agent will announce
+itself to you on boot.