'handoff' 검색 결과

Use when designing or reviewing Agentforce topic (renamed subagent in April 2026) structure, including topic boundaries, instruction quality, handoff rules, out-of-scope behavior, and topic-selector strategy. Triggers: 'agentforce subagents (formerly topics)', 'topic design', 'topic selector', 'agent scope boundary', 'handoff conditions'. NOT for restricting what the agent may do or say (topic Scope, action filters, abuse prevention) — use agentforce/agentforce-guardrails. NOT for the mechanics of transferring a live conversation out — Omni-Channel routing and the context package — use agentforce/agentforce-agent-handoff-patterns.

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

Use when designing how an Agentforce agent transfers the conversation to a human agent (Omni-Channel), to another bot/agent, or to an alternate workflow — including context package, deflection, escalation triggers, and user messaging. Triggers: 'agent to human handoff', 'agentforce escalate to omni channel', 'agent to agent handoff', 'transfer conversation with context', 'agent deflection fallback'. NOT for topic scope and selector design — use agentforce/agent-topic-design. NOT for the overall Einstein Bot plus Agentforce estate topology — use architect/conversational-ai-architecture.

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

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

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

Create and commit a durable handoff document that gives a fresh agent the context and prompt to continue the current planning or implementation work. Use only when explicitly invoked as `$handoff` or when the user explicitly requests a handoff.

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

Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.

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

Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a synced folder with a short seed prompt. Triggers: "/handoff", "prepare a handoff", "hand this off".

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

Prepare a private handoff to continue a task in Claude Code, Codex, or another agent; resume from an existing handoff without changing Git or executing its commands automatically. Use for "continue in Codex", "pasar a Claude", "migrar esta sesión", or "retomar este handoff".

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

Write concise next-agent handoff summaries across sessions, tools, and coding agents. Load when the user says handoff, next agent should know, save context, summarize where we are, switching agents, before ending a meaningful session, or when the user asks to commit, push, commit and push, create a git commit, push to origin, or publish commits — commit/push requests MUST run this skill first to prepare handoff docs, then proceed with git operations.

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

진행 중인 대화를 인계용으로 요약하고 민감한 정보를 제외한 뒤 새 백그라운드 에이전트에 전달합니다. 다음 작업의 초점과 참고 자료를 정리해 현재 작업 위치에서 이어 갑니다.

• 새 에이전트에 후속 작업 인계
• 다음 세션의 작업 범위를 좁혀 인계
• 다음 세션에 필요한 참고 자료 정리

참고 이미지와 막연한 취향을 색상·글꼴·배치 등 구체적인 디자인 방향으로 정리합니다. 재사용할 DESIGN.md와 제작 담당자를 위한 인계 자료를 만듭니다.

• 참고 이미지로 앱의 외형 결정
• 리디자인 전에 판단 기준 정리
• 슬라이드 디자인 방향 인계

Prepare a design handoff package for a developer using Claude Code. It documents screen layouts, visual details, interactions, and state requirements in a README.md, alongside reference files for implementation in the target app.

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

• Handing HTML prototypes to a developer
• Documenting precise visual details for implementation
• Explaining screen interactions and state requirements

Organize treatment decisions already supplied and verified by authorized licensed professionals into local JSON documents. Check document structure, source references, declared review status, and supplied dates to support documentation handoffs without making clinical decisions.

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

• Organize verified clinician-authored treatment records
• Check source references and missing documentation fields
• List checkpoint dates already supplied by clinicians

Review an existing security case package before report handoff. Check links between evidence, findings, investigation paths, tasks, and timeline entries, optionally verify file hashes to detect changes, and produce a Markdown or JSON review.

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

• Reviewing investigation records before report handoff
• Checking links between evidence, findings, and paths
• Verifying case artifact integrity with SHA-256

Create a ready-to-paste prompt for another agent or a later session to continue development work. Ground the handoff in current repository evidence, distinguish verified results from hypotheses and blockers, and identify uncommitted files and next steps.

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

• Ending a session with unfinished development work
• Handing a branch over to another agent
• Preparing instructions for a later session

Develop an implementation plan through sequential Planner, Architect, and Critic reviews. Compare options, document risks and acceptance checks, and preserve the plan and review records for a later handoff to `$ultragoal`.

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

• Compare approaches before implementation
• Plan testing and failure scenarios for high-risk changes
• Review a plan without starting implementation

Create a consistent UI design system from brand colors. Generate design tokens, reusable values for colors, typography, and spacing, and support component documentation, responsive layout calculations, accessibility considerations, and clear handoff materials for developers.

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

• Generate shared design values from brand colors
• Standardize typography and spacing across screens
• Plan layouts for different screen widths

Turn descriptions and existing notes into a standard operating procedure, a document explaining how work gets done. Capture process flow, responsibilities, detailed steps, exceptions, and metrics so teams can use it for handoffs or audits.

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

• Documenting a process known only to one person
• Clarifying who performs and owns each step
• Preparing procedures for handoffs or audits

Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.

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

• Prepare an end-of-day release handoff
• Consolidate documentation for merged changes
• Review unfinished work and verification status

Create, edit, and validate SDFormat files that describe robots and simulation worlds. Check coordinate frames, joints, geometry, and physical properties, review models in CAD Viewer, and report assumptions and compatibility risks before simulator handoff.

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

• Create reusable robot models or simulation worlds
• Review coordinate frames, joint axes, and inertial properties
• Validate SDF files and inspect models in CAD Viewer

Reconcile project documentation, agent rules, authorized memory, and workspace leftovers with current code and runtime behavior. Prepare a clear handoff by correcting stale information, identifying authoritative explanations, and reporting what is verified, pending, or awaiting cleanup approval.

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

• Synchronizing documentation after development
• Resolving stale or conflicting agent rule files
• Preparing a handoff to another person or a fresh session

Create and audit the files and routines that guide coding agents across sessions. It organizes instructions, progress tracking, verification, scope boundaries, and handoffs, with scripts for setup, structural checks, and shareable assessment reports.

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

• Creating AGENTS.md or CLAUDE.md and supporting files
• Preserving progress between agent sessions
• Defining checks required before work is marked complete

Design systems where multiple agents work with separate task information. Choose coordination structures, define handoffs and shared state, and plan parallel work while checking whether communication costs and failure risks justify using more than one agent.

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

• Split large tasks across separate agent contexts
• Run independent research tasks in parallel
• Define handoffs between specialized agents

Prepare a structured JSON handoff for bug fixes or pull request reviews. Capture outcomes, test evidence, change impact, publication status, and remaining work so the next person or workflow can understand what is complete and what remains.

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

• Handing off a completed bug fix
• Recording an existing pull request review
• Documenting unresolved checks and remaining work

Review how an AI agent loads, retains, summarizes, and shares working information. This historical guide helps examine forgotten constraints, repeated actions, tool selection, and handoffs using context engineering practices published in 2024–2025.

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

• Reviewing information loaded at startup versus on demand
• Investigating repeated actions or forgotten constraints
• Planning summaries and persistent task notes