Menu
How a coordinator delegates work, manages peer context, and verifies activation beyond the messaging mechanics in AGENTS.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Crear, abrir y mantener un JSON canónico conversacional en VisualSpecs, con componentes y relaciones que se actualizan mientras avanza una charla, sin modificar el código ni la configuración de la aplicación. Usar cuando el usuario quiera visualizar una idea viva en VisualSpecs o pida levantar la app apuntando a un canónico.
Before asking the user to choose between two or more options that differ in anything visual, spatial, or UI/layout-related, first build a quick self-contained HTML artifact that shows the CURRENT state and each option side by side (with a selector to switch), to scale and with honest metrics, so the user decides with the picture in front of them. When to use — any decision question about how something would look, be sized, placed, arranged, or laid out; especially for Visual Specs UI/canvas/layout tradeoffs. Load right before an AskUserQuestion whose options a person could see.
Start, verify, and open the local Visual Specs application from whatever CodebaseConstellation checkout the caller is working in. Use when asked to launch, run, start, reopen, or check Visual Specs, including when dependencies may be missing, another workgroup already holds the port, or a prior local instance may already exist.
Git, issue-branch, PR and version mechanics for Visual Specs repositories. Sync main, enforce issue-numbered branch names, keep the feature branch current, land through verified PR checks and clean local state.
Canonical Visual Specs delivery workflow. Confirm the change, assign one owner per artifact, use the constructive and adversarial gates, and land an issue-backed branch through a verified PR.
How a coordinator scopes a new request before delegating. Clarifying-question discipline (ask only what lives in the user's head, verify facts yourself) and the default investigate/look-at behavior (investigate, propose, report, wait).
| name | agent-coordination |
| description | How a coordinator delegates work, manages peer context, and verifies activation beyond the messaging mechanics in AGENTS.md. |
| when_to_use | Load before delegating to or messaging any workgroup peer. |
Use the current session AGENTS.md > Inter-Agent Messaging section as the authoritative source for peer discovery, --to values, file-based sending, and CLI syntax. If list-peers-lean returns no peers, stop and report it. Include the full repo path when the task touches a repo. State the objective, scope, constraints, and expected reply or artifact, or say explicitly that no reply is needed.
purge-wg to reset eligible workgroup peer sessions. Use --dry-run to preview the gate table. If a peer emitted output within the quiet period, purge-wg exits 3 and resets nobody; stop and close the prior work instead of forcing it. Avoid --graceful, which stalls inter-agent messaging daemon-wide.purge-wg. Preserve peer context through acknowledgment, report, revision, and review. Reset only a stale or bloated idle peer: try send --command clear; if unsupported, use close-session, then let the next send --mode wake cold-spawn it.After sending work, wait 45 seconds and run list-peers-lean; working: true confirms activation, not completion. If inactive, check for a reply or blocker; if neither exists and the peer is idle and reachable, follow the current Coordinator Context retry and rerouting rules. Once active, do not poll. When waiting, tell the user which peer and expected reply are pending.