Results for “coordination”

Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern no longer fits, user feedback reveals workflow gaps, a specialized variant is needed alongside the original, or agents have been added or removed from the library affecting team composition.

The English summary is being prepared. Showing the original description.

Apply collective intelligence coordination patterns — stigmergy, local rules, and quorum sensing — to organize distributed systems, teams, or workflows without centralized control. Covers signal design, agent autonomy boundaries, emergent behavior cultivation, and feedback loop tuning. Use when designing distributed systems without a coordination bottleneck, organizing teams that must self-coordinate, building event-driven architectures with shared state communication, or replacing fragile centralized orchestration with resilient emergent coordination.

The English summary is being prepared. Showing the original description.

Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordination shape is unclear, when you need topology-native breakdown instructions instead of a generic DAG, or when planning topology and runtime topology may differ. NOT for actual execution, node-level skill matching, or framework/tool installation.

The English summary is being prepared. Showing the original description.

AI-powered calendar management and agent-based scheduling coordination. Covers calendar APIs (Google Calendar, CalDAV/iCal), AI scheduling assistants (Reclaim, Clockwise, Motion, Cal.com), building custom calendar agents with MCP, multi-calendar merging, timezone management, focus block protection, meeting fatigue detection, and agent-to-agent meeting negotiation protocols. Activate on: "calendar agent", "AI scheduling", "calendar coordination", "meeting scheduling", "calendar API", "focus time protection", "calendar optimization", "Google Calendar MCP", "Reclaim", "Clockwise", "Motion", "Cal.com", "smart scheduling", "calendar-aware agent", "timezone scheduling", "agent negotiation meetings". NOT for: manual calendar UI component design (use form-validation-architect), project management scheduling or Gantt charts (use project-management-guru-adhd), general time-tracking or pomodoro apps (use adhd-daily-planner for time-awareness), building the agent itself from scratch (use agent-creator).

The English summary is being prepared. Showing the original description.

Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordination shape is unclear, when you need topology-native breakdown instructions instead of a generic DAG, or when planning topology and runtime topology may differ. NOT for actual execution, node-level skill matching, or framework/tool installation.

The English summary is being prepared. Showing the original description.

Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).

The English summary is being prepared. Showing the original description.

Install Port Daddy's bounded interactive coordination hooks ("tentacles", from the Giant Squid Harness) into the INTERACTIVE sessions of agentic coding CLIs (Claude Code, Codex, Gemini, Antigravity/agy) by auto-detecting which CLIs are installed and writing PER-PROJECT hook config behind a runtime gate, so coordination fires only inside a Port Daddy project while the daemon is running — never machine- wide-always-on. Use when the user says "install port daddy hooks", "agent CLI hooks", "interactive session hooks", "make coordination hooks fire in interactive sessions", "codex/gemini/agy hooks", or "auto-detect agent CLIs". NOT for generic software/package installation; NOT for installing the Port Daddy daemon or `pd` CLI itself (delegate to the `port-daddy` skill / `pd setup`); NOT for MCP server setup (delegate to `pd mcp install`); NOT for authoring new skills (delegate to `skill-architect` / `skill-creator`); NOT for editing the tentacle scripts themselves (owned by the Giant Squid Harness program; this installer layer is pd-adr-090).

The English summary is being prepared. Showing the original description.

Automate checks, code formatting, agent coordination, and session records around Claude Code operations. Uses hooks, actions triggered before or after work, to preserve context and connect development tasks with shared memory.

• Automatically format and validate edited code
• Share progress across multiple agents
• Save and restore development sessions

Connect RuView sensing data to AI agents through tools for presence, breathing, and heart rate. Explore agent coordination and prototype storing agent state and decisions alongside sensing data in a shared RVF container.

• Read live presence and vital-sign data from an agent
• Prototype agent responses to room-presence events
• Design coordination between sensing subagents

Coordinate multiple AI agents by adjusting their communication structure and task assignments as workloads change. The skill describes performance monitoring, switching coordination patterns, forecasting agent capacity, and validating changes with rollback when performance worsens.

• Choosing a coordination structure for multiple agents
• Redistributing tasks when agent workloads become uneven
• Forecasting how many agents a workload needs

Organize complex work across specialized agents with claude-flow. Start and stop agents, check their status and metrics, and manage groups by role, using shared memory to coordinate tasks such as development, reviews, and security checks.

• Assign bug fixes across research, coding, and testing agents
• Coordinate agents for feature development and review
• Organize specialists for security checks

Automate checks, code formatting, agent coordination, and session records around Claude Code operations. Uses hooks, actions triggered before or after work, to preserve context and connect development tasks with shared memory.

• Automatically format and validate edited code
• Share progress across multiple agents
• Save and restore development sessions

Portfolio mapping and model coordination in OpenConstructionERP: the 3D geo hub (Cesium), the coordination hub with clash AI, and geo-anchored projects. Use for multi-project portfolio views and BIM clash workflows.

The English summary is being prepared. Showing the original description.

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

The English summary is being prepared. Showing the original description.

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db / dispatch_tracker.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

The English summary is being prepared. Showing the original description.

Use this skill when mapping care coordination process requirements for Health Cloud: designing care team workflows, transition of care handoffs, social determinants of health (SDOH) barrier tracking, and care gap identification. NOT for building care plan templates, problems, and goals — use admin/care-plan-configuration. NOT for referral routing and provider networks — use admin/referral-management-health.

The English summary is being prepared. Showing the original description.

Comprehensive reference for inter-process communication mechanisms -- every way processes can talk on a computer. Covers sockets (TCP, UDP, Unix domain), WebSockets, SSE, pipes (named/anonymous), shared memory (mmap, shm_open), message queues, signals, D-Bus, XPC (macOS), gRPC, REST, stdin/stdout, file-based coordination, and clipboard. Performance benchmarks, platform availability, and code examples for each. Special focus on which IPC works best for AI agent coordination. Activate on: "IPC", "inter-process communication", "process communication", "how do I talk between processes", "Unix socket vs TCP", "shared memory", "named pipe", "WebSocket vs SSE", "gRPC vs REST", "agent coordination IPC", "XPC service", "message passing", "stdout pipe", "D-Bus", "mmap". NOT for: distributed systems design (use distributed-systems), network protocol design (use networking), message queue infrastructure like Kafka (use data-pipeline-engineer).

The English summary is being prepared. Showing the original description.

Benchmark multi-agent coordination systems with experiment design, power analysis, human rating protocols, bootstrap confidence intervals, and reproducible reporting. Use for salvage latency, recovery fidelity, coordination overhead, and protocol comparison studies. NOT for ML model benchmarking, web-product A/B testing, survey design, or general-purpose data science.

The English summary is being prepared. Showing the original description.

Choose multi-agent architectures using environment-first analysis, coordination pressure, commitment tuning, and knowledge levels. Use for autonomy design, protocol choice, and coordination failures. NOT for single-agent planning, centralized schedulers, or prompt-only swarms.

The English summary is being prepared. Showing the original description.

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues

Create and improve GitHub Actions workflows for automated testing and deployment. Coordinate multiple AI agents to review pull requests, investigate failed runs, scan for security issues, and manage releases across repositories.

• Create workflows for automated testing and deployment
• Investigate failed runs and suggest fixes
• Coordinate code reviews and security checks

Coordinate changes across multiple GitHub repositories with teams of AI agents. Align package versions, synchronize documentation, standardize project structures, and organize integration tests and pull requests for updates that affect several projects.

• Aligning dependency versions across repositories
• Synchronizing shared documentation
• Standardizing repository structures and CI workflows

Coordinate meetings across participants and time zones by checking availability and travel buffers, proposing suitable times, and creating or updating authorized events. Read back calendar details before preparing participant notification drafts.

• Finding meeting times across several participants
• Coordinating schedules across time zones
• Updating the details of an existing meeting

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues