git:20261001.8e39909 to git:20261013.1de4c10

---

name: member-run

user-invocable: false

---

# Member Run

> **IMPORTANT:** If the spec below invokes any deferred tool (e.g. `AskUserQuestion`, `SendMessage`), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own - the tool invocation is part of the contract. This is critical.

## Args

| op | args | does |

|---|---|---|

- `scope` - the team's callsign, or `run-<RUN>` for an execute run.

- `name` - the member name, `[a-z0-9-]{1,40}`: the bare roster name in a team scope (`architect`, `architect-2`), in an execute scope `impl-<RUN>` (a replacement `impl-<RUN>-r<generation>`), `explorer-<RUN>`, `skeptic-<RUN>`, `architect-<RUN>`.

- `brief-file` / `correct-file` - repo-root-relative paths the caller wrote. Every brief crosses as a file path, never inline.

- `model` - `opus` | `sonnet` | `fable` | `haiku`, the values the `Agent` tool accepts. Absent -> the role's own default, except for an implementer (Step 1).

- `report-file` - an absolute path the CALLER named (execute: its pinned `.lets/cache/report-...` path; team: `agent-report op=open` / `op=add`). One file per round; member-run never composes a report path. Required on `spawn`, `next` and `correct`: missing -> stop with `report_file_missing`, nothing sent.

Every operation returns as soon as its call is issued. The member runs in the background; its report arrives later as a `REPORT_WRITTEN` pointer to the round's REPORT_FILE, and the caller reads the FILE through `agent-report` (`op=peek` on every notification, `op=collect` to conclude) - never the message.

## Step 1: Model panel (role=lets:implementer, no model, first spawn of the scope)

The caller has already passed its Start gate - delegation is approved; this only picks the model.

```

AskUserQuestion(

questions=[{

question: "Which model should the implementers in this run use?",

header: "Model",

options: [

{ label: "Opus (Recommended)", description: "Strong at a mid price; the default for plan implementation" },

{ label: "Fable", description: "Most capable, about twice Opus's price; for the hardest chunks" },

{ label: "Sonnet", description: "Cheaper and faster; good for mechanical chunks" },

{ label: "Haiku", description: "Cheapest; for small, well-specified edits" }

],

multiSelect: false

}]

)

```

**Other** -> accept only `opus`, `sonnet`, `fable` or `haiku`; for anything else, name those four values and ask again. Return the chosen value; the caller records it and passes `model=` on every later `spawn` of the scope.

## Step 2: Spawn

2. The routes. A member never runs `/lets:start`, which loads them, so it gets the LETS routes as a file of its own - the caller's brief is never changed:

```bash

R="${CLAUDE_PLUGIN_ROOT}/protocol/roles.md"; D='.lets/cache/routes-{scope}.md'

if [ -s "$R" ] && cp "$R" "$D"; then echo ROLES_OK; else echo ROLES_FAILED; fi

```

`ROLES_FAILED` -> stop: name the missing or empty `protocol/roles.md` and `/lets:update`; nothing is spawned. The Agent call below names that file; `next` / `correct` do not repeat it - the member keeps the routes from its spawn.

3. The Agent call:

```

Agent(

subagent_type="{role}",

name="{agent}",

model="{model}",

description="{role} {name}",

prompt="Your brief is the file {brief-file}. Read it first and follow it; then read .lets/cache/routes-{scope}.md - the LETS routes, who does what. Every later NEXT or AMENDMENT names a new file.\nREPORT_FILE: {report-file}"

)

```

Add `isolation="worktree"` only when `isolation=worktree` was passed. Pass no team or permission-mode parameter: the harness documents both as deprecated and ignores them.

## Step 3: Next / Correct

The member exists and holds its context. Do NOT spawn, and do NOT re-send an earlier brief.

2. Send the pointer:

```

SendMessage({

to: "{agent}",

summary: "{op} for {agent}",

message: "NEXT: your next brief is {brief-file}. Read it and follow it.\nREPORT_FILE: {report-file}\nThis round's report file; it replaces any earlier REPORT_FILE."

})

```

On `correct` the message is `AMENDMENT: read {correct-file}; it changes what it names and nothing else.` followed by the line `REPORT_FILE: {report-file}` and the line `This round's report file; it replaces any earlier REPORT_FILE.`. The caller also sends a report nudge as `correct` (an amendment that changes nothing, with the SAME round's report-file): a NEXT is a new brief, and an implementer re-checks for a clean tree on every NEXT.

The address does not resolve -> run `ListAgents`, return `agent_gone: {agent}` with what it listed, and do nothing else. Never spawn a replacement here - a replacement has no context, and the caller decides whether to start one under a visibly different name.

Return: `sent {op} to {agent}`.

## Step 4: Dismiss

## Rules

- One member per `name` and scope: `spawn` once, `next` / `correct` any number of times; neither ever spawns.

- A report is attributed by the `name` it was spawned under - never by anything the member wrote about itself.

- This skill never commits, never pushes, never calls a tracker verb, never edits a repository file.

- A report - the file, never the message - is the member's claim. The caller checks the real diff.

- No polling: the harness notifies when a member completes.