excitedjs

Deterministic multi-agent orchestration with workflow_run, workflow_status, workflow_stop, and workflow_list. Load for staged, parallel, or pipelined TeamMate work that should produce one terminal result.

The development process for changing the dreamux repo itself, for a TeamLeader coordinating TeamMates. Use when implementing any non-trivial change — a feature, a refactor, or a fix. Covers landing a spec, resident-panel review across spec, implementation, fixes, and exact final heads, opening a PR to the default branch, and the gate before the operator sees it.

MCP operation notes for Dispatcher orchestration. Load before using TeamMate, Team, channel, or cron tools, including spawning or messaging TeamMates, creating or routing Teams, replying through provider-exposed channel tools, and managing cron jobs.

MCP operation notes for Team work. Load before using this Team's TeamMate tools, provider-exposed channel tools, cron tools, or Team channel binding tools.

Dreamux host operation notes. Load when diagnosing or operating dreamux serve, daemon startup, doctor/status results, dispatcher health, missing replies, stuck turns, restart behavior, config/state/run/log paths, bundled-skill injection, access state, or runtime app-server readiness.

Manage dispatcher-style coordination across sibling git repos from a parent workspace. Use when the user asks to spawn, dispatch, message, resume, inspect, compact, or kill Claude/Codex teammates; run one-shot Codex pool work with tm ask; coordinate work across sibling repos; check teammate state; or query teammate history. Also use when the user names dispatcher concepts such as "send out a teammate / spin up a teammate / dispatch a task / check what X is doing / multi-repo / dispatcher".

Periodic self-review of the dispatcher's own conversation history. Surfaces uncaptured corrections, recurring foot-guns, and drifted conventions, and promotes each finding into the right carrier (CLAUDE.md, project memory, or local dispatcher notes). Trigger when the user asks to "复盘 / 自我反省 / 派活流程审查 / review dispatcher / optimize dispatcher / let dispatcher self-reflect / /claudemux:optimize", or when a scheduled cron callback fires the periodic review.

Understand and operate Feishu channel ownership handoff between a dispatcher and teammate sessions. Use when the user wants to talk directly to a teammate through the Feishu channel, hand the channel back to the dispatcher, check who currently owns the channel, recover a dead teammate owner, or asks about "飞书 channel 交接 / channel ownership / 交还 dispatcher / 让我和 TM 直接说 / 把 channel 还给 dispatcher".

Manage who may reach a Claude Code session through the Feishu channel — approve a pairing code from a first-time direct-message sender or an unconfigured group, manage the allowlist, and set the group-message policy (block, allowlist, or follow-user). Use when the user wants to approve, pair, allowlist, or block a Feishu sender or group, change how group messages are gated, received a pairing code, or asks why a Feishu message was not delivered. Also use for the Chinese phrasings — "飞书配对 / 通过配对码 / 飞书 allowlist / 批准飞书用户 / 飞书群授权 / 飞书群配对 / 飞书群权限模式".

Use when the user wants to add a requirement, change a requirement, refine acceptance criteria, split implementation scope, or clarify delivery boundaries. Trigger proactively on requests like “加需求”, “补一个需求”, “做个新需求”, “改下需求”, “需求拆一下”, “补验收标准”, or any request that is really about shaping product or engineering requirements before or alongside implementation.