herdr-orchestratorlisted

# Herdr Orchestrator User-invoked, question-first skill. It explains the live Herdr setup, asks which panes and models to use, creates the requested two-tab layout, then orchestrates Council planning and Codex goal execution. It does not silently choose agents or models. ## Done condition Orientation/setup is complete only after: - Herdr caller context is verified. - Current workspace, tabs, panes, agents, cwd, and lifecycle states are read. - User confirms the Main and Council Agents tab layout. - User selects or confirms the model/integration for every new pane. - Exactly three non-OpenCode Council targets are identified. - Codex goal target and durable goal cursor are identified. - Pause-on-milestone and user-continue behavior are confirmed. - The first dispatch and verification command are written. Missing facts become one targeted question. Never infer identity from sidebar position, stale chat, or model labels. ## 1. Herdr boundary Herdr owns workspaces, tabs, panes, PTYs, recognized agents, focus, lifecycle state, and terminal persistence. Grok observes and dispatches through Herdr; Grok does not invent a second terminal/session authority. Run inside a Herdr-managed pane: test "$HERDR_ENV" = 1 If this fails, report that the caller is outside Herdr and stop. Do not inspect or control another Herdr session from outside. Read installed command authority: herdr --help herdr --skill Never run bare herdr for discovery; it launches or attaches the TUI