owl-listener/ai-design-skills

handoff-protocols

Designing smooth transitions between agents and between AI and humans.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/owl-listener/ai-design-skills --skill handoff-protocols

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Handoff Protocols

A handoff is the moment one agent passes work to another — or to a human. It's where multi-agent systems most commonly fail. A dropped handoff means lost context, repeated work, or abandoned tasks.

Anatomy of a Handoff

Every handoff has:

  • Trigger: What causes the handoff? (task completion, scope boundary, failure, user request)
  • Source: Who is handing off?
  • Destination: Who is receiving?
  • Payload: What information transfers? (context, partial results, user state, instructions)
  • Acknowledgment: How does the source know the destination received the handoff?
  • User experience: What does the user see during the handoff?

Handoff Types

  • Sequential: Agent A finishes, passes results to Agent B who continues. Like a relay race.
  • Parallel fan-out: One agent distributes subtasks to multiple agents simultaneously.
  • Parallel fan-in: Multiple agents' results converge back to one agent for synthesis.
  • Escalation: An agent can't handle the task and passes up to a more capable agent or human.
  • Fallback: The primary agent fails and a backup takes over.
  • Human handoff: AI passes work to a human for review, decision, or completion.

Context Transfer

The most common handoff failure is context loss. Design what transfers:

  • Full context: Everything the source agent knew. Safe but potentially overwhelming.
  • Summarised context: Key information distilled. Efficient but risks losing important nuance.
  • Structured context: Predefined fields that must be populated. Consistent but rigid.
  • Incremental context: Only what's new since the last handoff. Efficient for ongoing collaborations.

Designing for the User

The user's experience of handoffs matters:

  • Invisible handoff: The user doesn't know agents changed. The experience feels seamless.
  • Transparent handoff: The user is told a new agent is taking over and why.
  • Participatory handoff: The user confirms the handoff or provides additional context.
  • User-initiated handoff: The user explicitly requests a different agent or a human.

Handoff Anti-Patterns

  • The black hole: Work is handed off but never picked up
  • The echo chamber: Agents hand work back and forth without progress
  • The context cliff: Critical information is lost in the handoff
  • The jarring transition: The user's experience changes dramatically at the handoff point
  • The silent redirect: The user doesn't know they've been handed off and gets confused by changes

Design Artefacts

  • Handoff protocol specifications (trigger, source, destination, payload, acknowledgment)
  • Context transfer templates
  • Handoff sequence diagrams
  • User experience specifications for each handoff type
  • Handoff failure mode analysis
같은 저장소의 Skills

더 많은 Skills

모든 Skills