conduct

Files (12)

• SKILL.md
• adopt.md
• openai.yaml · agents/
• conductor-core.md
• dispatch.md
• lane-rows.html
• backend.md · roles/
• designer.md · roles/
• frontend.md · roles/
• generic.md · roles/
• orchestrator.md · roles/
• qa.md · roles/

SKILL.md (first lines)

# Conduct — Orchestrate the Session Through Workers

The invoking session is the senior. It coordinates and never does project
work itself. `/conduct` hands each task to a worker and returns so the senior
session stays available. A worker is a background `Agent` subagent in this
session, or an `hq lanes` worker lane (a separate process). Both runners get
the same brief, the same done criteria, and the same verification step.

### Routing

Owner decision, 2026-10-22 ("Workers stay open"). This replaces the
2026-10-07 triage that kept reads, lookups, and short skills inline.

- Inline only: an answer from context already loaded, or one status read.
- Standing worker lane: any task that matches an HQ worker in the registry or
  a `--workers` role, and any ongoing area of work in that worker's scope.
  Open it early, keep it open with
  `hq lanes keep-alive <lane> --on --standing`, and send later tasks for the
  same worker and company to the same lane instead of opening another.
- Background subagent: a small, bounded task with no matching worker (a
  lookup, a check, a draft, one skill run).

`bash core/scripts/conduct-standing.sh route --kind <answer|status|lookup|small|ongoing>
[--worker <id> --company <slug>]` applies these rules for the session's runner and names the standing
lane to reuse. `conduct-standing.sh send` opens or reuses the lane. See
"Standing worker lanes" in `dispatch.md`.

### Runner choice

Owner decision, 2026-10-22: `mixed` is the default runner.

- `mixed` (default): the routing above. Standing worker lanes, kept open with
  keep-alive, take ongoing areas and tasks that match an HQ worker or a
  `--workers` role. Background subagents take small bounded tasks. Nothing
  runs inline beyond an answer from loaded context or one status read.
- `subagent`: the brief runs as a background `Agent` subagent in
  this session. It starts at once, uses this session's own Claude login, and
  is never refused for lane capacity. It shares this session's usage and stops
  if this session ends.
- `lane`: the brief runs through `hq lanes create`. Use it when the owner asks
  for lanes, when the work must outlive this session (overnight work, lead
  lanes that resume on their own, `--loop`, `--remote-control`, `--outpost`,
  or a non-Claude engine), or when the host has no `Agent` tool (Codex).
- A lane create that comes back with `no_account_with_room` or another
  admission or capacity refusal falls back to a subagent with the same brief.

Resolve the runner from the `conduct_runner` session pin, then
`conduct.runner` in `personal/settings/orchestrator.yaml`, then
`core/settings/orchestrator.yaml` (ships `mixed`), then `mixed`.
See "Runner" in `dispatch.md`.

## Step 1: Parse the argument

- `off` → close the standing lanes with
  `bash core/scripts/conduct-standing.sh close` (keep-alive off, then
  interrupt, so a later create resumes the worker's thread), stop each other
  lane this session launched after confirmation, clear the session engine
  pin, and close an open session link with
  `hq lanes link close --link <link-id> --session-id <session-id>`.
- `status` → report this session's lanes from `hq lanes list --json`, its
  standing lanes from `conduct-standing.sh list`, and its running subagents;
  do not launch work.
- `--runner mixed|subagent|lane` → pin the runner for this session with
  `bash core/scripts/hq-session.sh set conduct_runner <runner>`. The remaining
  words are the task.
- `adopt` → use `.claude/skills/conduct/adopt.md` for linked-session behavior.
- `tell {child} {message}` → send through `hq lanes link send` with the same
  link, child, session, and text flags:
  `hq lanes link send --link <link-id> --child <child> --session-id <session-id> --text <message>`.
- `--workers {roles}` with optional `--engine`, `--model`, `--effort` → pin
  the selected provider/model/effort once for this session using
  `bash core/scripts/lanes-workers.sh setup`, then open one standing lane per
  role with `conduct-standing.sh send` before the first task. The remaining
  words are the task.
- An explicit `--engine`, `--model`, or `--effort` applies to this session and
  overrides its existing pin. Mark `conduct_default_source` as `explicit`.
- An account the user names for the session is stored as
  `conduct_child_account` with `hq-session.sh set`, next to
  `conduct_child_model` and `conduct_child_effort`. With no account pin and no
  `--account` flag, every lane is created with `--account auto`. See
  `dispatch.md`.
- When a create or route response lists a signed-out account under
  `skipped[]`, raise one exec-bus owner card per account with the `fix`
  command, deduped for 24 hours in one machine-wide file. Never run
  `hq capacity login` or sign an account in or out. See "Signed-out
  accounts" in `dispatch.md`.
- Otherwise, use an existing `conduct_engine` as-is. Codex SessionStart may
  provide `conduct_engine=codex` and the selected `conduct_child_model` and
  `conduct_child_effort`; when no model is supplied, leave it unset for the
  CLI's documented fallback.
- If the user switches an automatic Codex engine to another engine without
  naming a model or effort, clear those automatic pins before setting the new
  engine and mark `conduct_default_source=explicit`. The `--workers` path does
  this in `lanes-workers.sh setup`; for a plain `/conduct` dispatch, clear the
  unset pins with `hq-session.sh` before saving the explicit values.
- A first word matching a provider choice sets the session default; otherwise
  treat the full argument as the task. Resolve an unpinned provider at first
  dispatch, asking once only when no configured default or installed provider
  matches.
- No task text → confirm conduct mode and wait.

## When a task needs a worker

Every task except an inline answer or status read needs a worker. Read
`.claude/skills/conduct/dispatch.md` whole and follow it. It covers the
runner choice, standing lanes, worker selection, the shared lane mapping, task briefs,
subagent dispatch, lane creation, watcher setup, role lanes, QA, CI, result
verification, and status rows. It is not loaded for questions, lookups,
status, or `/conduct off`.

## Rules

- `/conduct` creates workers only: background subagents or worker lanes. The
  invoking session is the senior; do not create manager or senior lanes.
- The conductor does no project work inline: no file edits, builds, tests,
  multi-step searches, or skill runs in this session.
- Every lane is created with `--company <slug>`. Resolve the company first;
  a task with no company stays with the owner until one is named.
- Before `/handoff` or the session ending, run

From indigoai-us/hq-pack-core-skills, MIT.

More from indigoai-us/hq-pack-core-skills