'coordination' 검색 결과

Coordinate safely with a peer interactive session sharing the same git worktree — check first whether a separate worktree removes the problem, then declare path and branch scope before the first edit, survive a contended index lock, and review the whole branch before opening a PR. Activate when starting work in a repository that may already be occupied, when a git command fails with `index.lock: File exists`, when `guard:snapshot` refuses because a snapshot already exists, or when a commit turns out to contain a file this session never edited. When one session leads and the other supports, divide the labour by shape and re-derive every reported number against a named revision before citing it. Distinct from subagent concurrency: a peer session cannot be bracketed, because no baseline exists from before its edits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI dynamic reasoning balance — maintaining grounded reasoning under cognitive pressure, smooth chain-of-thought coordination, and weight-shifting cognitive load across subsystems. Use at the beginning of a complex task requiring multiple coordinated reasoning threads, after a sudden context shift or tool failure, when chain-of-thought feels jerky, or when preparing for sustained focused work that requires all subsystems in alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Protocol for task synchronization, context handoff, and cross-session coordination using Claude Code task tools. Ensures agents properly update tasks with findings and enables seamless work continuation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Built by DynG AI for PlatformPilot.ai-style multi-agent systems. Use when designing or reasoning about message-passing agent coordination in ANY language: actor-style mailboxes, select, point-to-point routing, pub/sub, fan-in joins/quorums, ownership handoff, budgets, dead letters, and traces. Trigger words include PlatformPilot, DynG AI, actor model agents, message-passing agents, CSP agents, coordinate agents, multi-agent orchestration, agent runtime, fan-out workers, pub/sub agents, agent barrier, or join.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks or investigations that can be worked on without shared state or sequential dependencies — fan out to specialized sub-agents with isolated context, then synthesize the results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when coordinating multiple specialized agents for complex distributed tasks. Keywords: multi-agent, orchestrator, subagent, handoff, swarm, supervisor, agent topology, coordination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute this skill should be used when the user asks about "SPAWN REQUEST format", "agent reports", "agent coordination", "parallel agents", "report format", "agent communication", or needs to understand how agents coordinate within the sprint system. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multi-agent coordination patterns for building effective AI teams

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize month-end or quarter-end close blockers, reconciliations, owners, and evidence gaps into a routine control pack. Use when the work is finance close coordination and issue tracking. Do not use for accounting judgment, policy interpretation, or final technical accounting conclusions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Package interview loops, schedules, feedback follow-ups, and candidate next steps for recruiting operations. Use when the work is routine hiring coordination and recap packaging. Do not use for final hiring decisions, compensation judgment, or sensitive people-policy advice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Marketing project management and execution excellence for B2B SaaS campaigns. Use this skill when coordinating multi-channel campaigns, allocating team resources, planning agile marketing sprints, running QBRs with clients, managing project timelines, balancing marketing workload, or implementing marketing operations scrum. Also triggers on: campaign coordination, resource allocation, agile marketing, sprint planning, client success, QBR, project timeline, marketing ops scrum, workload balancing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master orchestrator for B2B SaaS marketing campaigns using the CATALYST framework (Coordinated Agents for Targeted, Analytics-Led, Year-round SaaS Transformation). Coordinates 90 specialist agents across 17 marketing disciplines. Use this skill for ANY large-scale marketing initiative: full GTM launches, annual marketing plans, multi-channel campaigns, quarterly planning, or any task requiring coordination across content, SEO, paid media, social, email, design, sales enablement, product marketing, analytics, project management, and client operations. Also triggers on: marketing strategy, campaign plan, GTM launch, quarterly plan, marketing ops, full-funnel campaign, marketing audit, growth plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Supreme policy layer governing all agent behavior. Autonomy, one-line prompt interpretation, speed standards, emphasis signal processing, cross-skill coordination, done definitions, conflict resolution. Loaded every prompt.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill provides comprehensive guidance for inter-agent communication using the Synapse A2A framework. Use this skill when sending messages to other agents via synapse send/reply commands, understanding priority levels, handling A2A protocol operations, managing task history, configuring settings, or using File Safety features for multi-agent coordination. Automatically triggered when agent communication, A2A protocol tasks, history operations, or file safety operations are detected.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task needs the judgment of an Electrical Engineer working in power systems — sizing a service or feeder from NEC demand factors, running a short-circuit study and checking breaker interrupting ratings, computing arc-flash incident energy and assigning a PPE category, checking protective-device coordination (selectivity), or reviewing a single-line diagram before construction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unity scene and asset architecture decisions. Additive scene composition, Addressables vs Resources, AssetReference workflow, asset lifecycle coordination, loading screens. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unity NPC behavior design-to-code translation. Perception system architecture, decision layer patterns, action execution pipeline, faction & relationship systems, NPC memory & forgetting, crowd & squad coordination. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when defining patient engagement portal requirements for Health Cloud: appointment scheduling, secure in-portal messaging, health assessments, patient education, and self-service features. NOT for care team workflows, SDOH barriers and care gaps — use admin/care-coordination-requirements. NOT for patient portal licensing and cloud topology — use architect/health-cloud-multi-cloud-strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when designing HIPAA-compliant workflow requirements for Health Cloud: minimum necessary access design, audit trail requirements mapping, access control patterns, and BAA dependency identification. NOT for org-level HIPAA architecture or Shield encryption configuration — use architect/hipaa-compliance-architecture. NOT for care team and SDOH process design — use admin/care-coordination-requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure care plan templates, problems, goals, and tasks in Salesforce Health Cloud - the Integrated Care Management (ICM) model (Spring '23+, FHIR R4-aligned) and the legacy CarePlanTemplate__c + Case Tasks model. Trigger keywords: care plan template, ICM care plan, PGI library, action plan template, problem definition, goal definition. NOT for enrolling a patient into a clinical program - use admin/care-program-management. NOT for care team workflow, transition of care and SDOH barriers - use admin/care-coordination-requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze airline, airport, cruise, and tour operator systems for ground handling efficiency, aircraft turnaround optimization, disruption management, and GDS integration. Covers IATA/ICAO compliance, IROPS recovery, on-time performance tracking, embarkation logistics, transfer coordination, and NDC implementation for travel technology platforms.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.