twining-coordinatelisted

# Twining Coordinate — Multi-Agent Delegation and Discovery You need work done by a specialized agent, or you want to understand what agents are available for a task. > **Requires the full tool surface.** Every tool in this skill — `twining_register`, `twining_agents`, `twining_discover`, `twining_delegate`, `twining_read`, `twining_recent`, and the deprecated `twining_handoff` / `twining_acknowledge` — exists only when the project sets `tools.full_surface: true` in `.twining/config.yml`. On a default install none of them are callable. Coordinate through the blackboard instead: `twining_post` a `need` entry describing the work, and have each agent `twining_assemble` on its scope before starting. Do not claim a delegation was registered when the tool was unavailable. ## When to Invoke - When a task requires capabilities beyond your own - When work can be parallelized across multiple agents - When you need to find an agent with specific expertise - When delegating a subtask to run in isolation ## Workflow ### 1. Discover Available Agents Call `twining_agents` to see all registered agents with: - Their capabilities (e.g., `["database", "postgresql", "migration"]`) - Liveness status (`active`, `idle`, `gone`) - Role and description ### 2. Find Matching Agents Call `twining_discover` with: - `required_capabilities`: Array of capability strings needed for the task - `include_gone`: Set to `false` to exclude agents that haven't been active recently (default: `true`) - `min_