Herdr Standup Skill

Process steps in order. Do not skip ahead.

A standup is not a round of work: nothing is dispatched, no context is cleared, and no worker is interrupted. A worker that is mid-task keeps working and its row comes from what you already know.

Each command resolves HS to its installed Herdr skill or that skill in a herdr-policy clone. Repeat the resolver in every call. Prose skills/... paths are relative to the package root.

Read the lookup rule before running these command blocks:

rules/herdr-bootstrap.md

Step 1 — Roster the Team

HS=.tessl/plugins/jbaruch/herdr-policy/skills/herdr-foreman/; [ -d "$HS" ] || HS="$HOME/$HS"; [ -d "$HS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/herdr-policy|git@github.com:jbaruch/herdr-policy.git|https://github.com/jbaruch/herdr-policy|https://github.com/jbaruch/herdr-policy.git|ssh://git@github.com/jbaruch/herdr-policy|ssh://git@github.com/jbaruch/herdr-policy.git) HS=skills/herdr-foreman/ ;; *) echo "herdr-policy skill not found: install jbaruch/herdr-policy" >&2; exit 1 ;; esac
bash "$HS/roster.sh"

Emits {"caller":{...},"agents":[{"name","kind","pane_id","state"}]} for every named agent other than your own pane. Exit 1 is a precondition (outside Herdr, herdr absent); exit 2 is a herdr failure. On either, report the message verbatim and finish here.

Split the roster by state:

• idle or done — ask them in Step 2.
• working or blocked — never asked. Their row comes from the round log or the assignment ledger, with what they are on, in Step 4.

An empty roster means there is no team to stand up. Say so and finish here. Proceed immediately to Step 2.

Step 2 — Ask Each Ready Worker

One call per idle or done worker:

HS=.tessl/plugins/jbaruch/herdr-policy/skills/herdr-standup/; [ -d "$HS" ] || HS="$HOME/$HS"; [ -d "$HS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/herdr-policy|git@github.com:jbaruch/herdr-policy.git|https://github.com/jbaruch/herdr-policy|https://github.com/jbaruch/herdr-policy.git|ssh://git@github.com/jbaruch/herdr-policy|ssh://git@github.com/jbaruch/herdr-policy.git) HS=skills/herdr-standup/ ;; *) echo "herdr-policy skill not found: install jbaruch/herdr-policy" >&2; exit 1 ;; esac
bash "$HS/standup-ask.sh" \
  <agent-name> <absolute-report-path>

Checks readiness without sending input and emits {"agent","report_path","state","sent"}. Herdr 0.9.2 lacks atomic readiness-guarded prompting. Exit 5 returns sent: false and reason: "atomic_prompt_unavailable"; use the round log in Step 4 and never substitute agent prompt or pane input. A sequence of idle reads grants no delivery authority. Exit 3 means the worker was not ready and nothing was sent — move it to Step 4's list. Exit 4 means the worker's live pane is too narrow for its REPORT: <path> line and nothing was sent; the JSON adds pane_width and needed. Relay both to the operator, who widens the pane or picks a shorter reports directory, and move the worker to Step 4's list. Exit 1 is a precondition, including a report path over the script's coarse length bound, exit 2 a herdr or measurement failure. On exit 1 or 2 nothing was sent: relay the diagnostic verbatim to the operator and move the worker to Step 4's list. The inspection/refusal contract is in the header of skills/herdr-standup/standup-ask.sh.

Proceed immediately to Step 3 with every worker whose ask exited 0. When no ask exited 0, skip Step 3 and proceed immediately to Step 4.

Step 3 — Wait for Each Answer

Wait for each worker asked in Step 2:

HS=.tessl/plugins/jbaruch/herdr-policy/skills/herdr-standup/; [ -d "$HS" ] || HS="$HOME/$HS"; [ -d "$HS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/herdr-policy|git@github.com:jbaruch/herdr-policy.git|https://github.com/jbaruch/herdr-policy|https://github.com/jbaruch/herdr-policy.git|ssh://git@github.com/jbaruch/herdr-policy|ssh://git@github.com/jbaruch/herdr-policy.git) HS=skills/herdr-standup/ ;; *) echo "herdr-policy skill not found: install jbaruch/herdr-policy" >&2; exit 1 ;; esac
bash "$HS/standup-wait.sh" \
  <agent-name> <absolute-report-path>

Same argv, stdout, and exit codes as wait-report.sh. The budget is the script's constant, never a number chosen here; see the header of skills/herdr-standup/standup-wait.sh. Exit 1 means the worker did not answer inside it. It is not chased twice. Move it to Step 4's list with what you know. Exit 3 means a dialog is up:

• Read the pane and follow skills/herdr-foreman/references/herdr.md Runtime Dialogs.
• After resolving an authorized action, re-read the same target and resume its wait after the dialog clears.
• Never resend the standup question.
• If that contract requires escalation, continue Step 4 with the worker's recorded state while it remains blocked.

Exit 5 means the report is unavailable after a confirmed provider refusal. Record it as missing in Step 4 and notify the operator; never automatically retry, rephrase, switch models/providers, or synthesize an answer. Exit 4 means the answer file exists but the pane did not show the marker whole. That is not an answer. Read the live state with herdr agent get <agent-name> and take the first continuation that applies:

• The command fails — report its message verbatim and finish here.
• The state is blocked or working — re-run the wait for that worker once. Other exits take their documented branches. A second exit 4 is terminal: move the worker to Step 4's list with what you know.
• The state is idle or done — move the worker to Step 4's list with what you know. standup-ask.sh refuses a marker the worker's live pane would wrap, so this outcome means the pane narrowed after the ask.

Proceed immediately to Step 4.

Step 4 — Write the Rows Nobody Answered

For every worker that was busy, blocked, or silent, write one entry into a JSON file for the renderer:

{
  "<agent>": {
    "roles": "developer",
    "done": "<from the round log>",
    "plan": "<from the round log>",
    "blocked": "none",
    "note": "busy: <task>"
  }
}

note renders beside the agent's name, so a busy worker reads as grok (busy: refactor). Every field is optional. Take the content from the round log or the assignment ledger — never from a pane read, and never from a guess about what a worker is probably doing. Use the foreman's schema-1 task ledger under skills/herdr-foreman/state-schema.md for accepted completion. Read it without writing or migrating it. Missing or unsupported records mean unknown completion; dispatch status alone establishes none. Worker DONE answers remain self-reports.

If every worker answered, skip the file. Proceed immediately to Step 5.

Step 5 — Render the Standup

HS=.tessl/plugins/jbaruch/herdr-policy/skills/herdr-standup/; [ -d "$HS" ] || HS="$HOME/$HS"; [ -d "$HS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/herdr-policy|git@github.com:jbaruch/herdr-policy.git|https://github.com/jbaruch/herdr-policy|https://github.com/jbaruch/herdr-policy.git|ssh://git@github.com/jbaruch/herdr-policy|ssh://git@github.com/jbaruch/herdr-policy.git) HS=skills/herdr-standup/ ;; *) echo "herdr-policy skill not found: install jbaruch/herdr-policy" >&2; exit 1 ;; esac
python3 "$HS/standup-render.py" \
  --reports <round-reports-dir> \
  --now <ISO-8601> \
  --team "<label>" \
  --agent <name>=<report-path> [--agent ...] \
  [--roles <roles-json>] [--extra <extra-json>]

Writes standup-<date>.md into the reports directory and prints one JSON object on stdout: {"markdown_path","block","answered","unasked"}, where block is the fenced terminal table. Save the output to a file. Exit 2 means a report file did not carry the four-line shape, naming the file — ask that worker again, or move it to --extra. Exit 1 is a missing or unwritable input, and the message says what to fix.

--now is required and never defaults to the clock, so the same inputs render the same bytes. The column widths and the wrapping are the script's contract; see the constants at the top of skills/herdr-standup/standup-render.py.

Proceed immediately to Step 6.

Step 6 — Relay the Block

Read saved attention using the team's recorded state override or default:

HS=.tessl/plugins/jbaruch/herdr-policy/skills/herdr-foreman/; [ -d "$HS" ] || HS="$HOME/$HS"; [ -d "$HS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/herdr-policy|git@github.com:jbaruch/herdr-policy.git|https://github.com/jbaruch/herdr-policy|https://github.com/jbaruch/herdr-policy.git|ssh://git@github.com/jbaruch/herdr-policy|ssh://git@github.com/jbaruch/herdr-policy.git) HS=skills/herdr-foreman/ ;; *) echo "herdr-policy skill not found: install jbaruch/herdr-policy" >&2; exit 1 ;; esac
bash "$HS/foreman.sh" catch-up [--state <state-file>]

Present nonempty attention_markdown before the table. Follow attention page counts and next_offset before claiming every pending item was shown. The read never resolves an item, updates a presentation marker, or contacts workers. On non-zero, report that saved attention is unavailable and its diagnostic; continue with the independently gathered standup. If there are no pending items, proceed silently. Its lifecycle contract is:

skills/herdr-foreman/references/attention.md

Print block from the saved output verbatim (jq -r .block <file>), exactly as the renderer emitted it. Do not reformat it, summarize it, or replace it with prose.

Name markdown_path underneath, in one line. Add a provenance line identifying worker-reported rows and rows whose completion was verified from the task ledger. Label unavailable acceptance evidence as unknown; dispatch records prove none. Add your own reading of the standup only if a row carries something the operator should act on today — a blocker naming another worker, or a plan that contradicts the round in flight. Otherwise the table speaks for itself. Finish here.