auto-office

Directly invocable Auto Office v3 Agy CLI mechanics primitive. Use when a selected/explicit Agy harness dispatch needs exact launch flag ordering, dynamic model discovery, model-dependent effort handling, workspace pinning, timeout/quota-stall diagnosis, prompt transport, recovery, or Agy-specific failure attribution. Do not treat this primitive as a separate lifecycle office or proof of adapter promotion.

Auto Office v3 harness-adapter engineering primitive. Use to add, validate, conformance-test, inspect, or promote a harness adapter; map model/effort identities; define safe invocation/prompt transport/quota probes/failure signatures; and enforce invalid, valid-unverified, and proven trust states without modifying the office lifecycle.

Internal Auto Office v3 closeout spoke. Use after implementation/review to reconcile findings, validate completion evidence, report branch/PR state and real blockers, record pinned runtime hashes and telemetry, enforce the human merge-to-main boundary, and finish family state without claiming success from model confidence alone.

Internal Auto Office v3 execution spoke. Use after an accepted plan to validate execution packets, acquire mutable role/write-scope ownership, dispatch executors or workers through the selected harness adapter, enforce protected paths and blast-radius limits, handle takeover/version checks, self-review mutations, and return durable evidence without widening scope.

Internal Auto Office v3 intake spoke. Use when the planner runs the interactive requirements interview before freezing intent — covering the twelve-item floor in one or two batched question rounds (or a structured-question tool, per harness) and deriving the five frozen fields from the answers. This spoke is planner-owned and requires talking to the user directly; it supersedes the older orchestrator-owned, planner-silent interview (issue-35#decision-1, overturning issue-47). Do not use to ask about gear, which is declared, not interviewed.

Internal Auto Office v3 loop-driver spoke. Use after plan approval to dispatch waves without blocking, integrate dispatch branches through a validated merge, adjudicate contract disagreements, and hold the autonomy ceiling — proceeding end to end while never merging to main without an explicit user statement.

Internal Auto Office v3 maintenance spoke. Use at the beginning or closeout of an Auto Office invocation to label eligible historical outcomes lazily, refresh stale model catalogs outside route-time, update local harness bindings, maintain hot/warm/dreamt evidence tiers, compute maturity/decay, and prepare replay inputs without requiring an always-running daemon.

Adaptive office engineering runtime for the complete lifecycle from intent through planning, routed execution, verification, independent review, and closeout. Use when explicitly invoked as /auto-office or when the user directly asks to run the Auto Office v3 lifecycle. Route each role by harness, model, and effort using pinned policy/catalog/adapter/config snapshots, hard capability and trust floors, live quota constraints, local evidence, and task shape. Preserve human merge-to-main, no-self-approval, durable handoffs, private telemetry, replay-gated policy changes, and isolated self-improvement.

Internal Auto Office v3 planning spoke. Use when the auto-office orchestrator needs to run interactive requirements discovery directly with the user, freeze the five execution fields, resolve product decisions, classify playbook/blast radius/size, produce or refresh a serialized implementation plan, or revise a plan after an accepted PLAN DEFECT. Do not use as a separate lifecycle or to change frozen requirements silently after freeze.

Internal Auto Office v3 independent review spoke. Use for plan review, code review, accepted-material/minor/rejected/pending finding disposition, pointed blast-radius and bypass analysis, repeated review rounds, or validating PLAN DEFECT and BRIEF DEFECT exits. Never reuse the producer session as its own independent reviewer.

Internal Auto Office v3 router. Use when selecting or explaining a role route across harness, model, and effort; evaluating adapter trust/capabilities/absolute floors/task shape/quota/advisory quality/cost/local evidence; deciding exploration eligibility; or recording a routing decision. Route-time must remain offline and reproducible from pinned snapshots.

Internal Auto Office v3 self-improvement primitive. Use only to create isolated learned-pattern or catalog/policy proposal work from historical evidence after deterministic sanitization, replay/evals where required, privacy lint, deterministic proposal identity, independent review, and lineage metadata. Never activate unmerged policy into the current run or merge its own proposal to main.

Internal Auto Office v3 verification spoke. Use to build or execute the verification floor for mutable work, choose targeted/regression/static/build/runtime checks, prove known-bad inputs fail critical gates, run browser acceptance flows for user-facing work, and package validation evidence for independent review and closeout.

Directly invocable Auto Office v3 Claude CLI mechanics primitive. Use when a selected/explicit Claude harness dispatch needs safe background/in-session launch behavior, prompt transport, worktree isolation, tool allowlisting, liveness, remote-control/resume handling, or Claude-specific failure attribution. Do not treat this primitive as a lifecycle office or proof of adapter promotion.

Directly invocable Auto Office v3 Codex CLI mechanics primitive. Use when a selected/explicit Codex harness dispatch needs safe model+effort invocation, worktree targeting, prompt transport, liveness/readback, resume safety, or Codex-specific failure attribution. Do not treat this primitive as a lifecycle office or as proof that the Codex adapter is proven.

Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.

Sweep Herdr panes that this same orchestrating pane spawned and that have finished, using the shared auto-office pane ledger. Use only when the user explicitly asks to close/sweep/clean up done Herdr panes, or when the herdr skill's spawn recipe tells you to. Requires HERDR_ENV=1 and the herdr skill already loaded.

Directly invocable Auto Office v3 Hermes CLI mechanics primitive. Use when a selected/explicit Hermes harness dispatch needs prompt transport, model selection, working directory targeting, liveness detection, completion readback, or Hermes-specific failure attribution. Do not treat this primitive as a separate lifecycle office or proof of adapter promotion.