'handoff' 검색 결과

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

Design workflows where specialized AI agents share recurring product management tasks. Define each agent’s role, required information, handoffs, and human review points, then create monitoring and evaluation plans for the overall workflow.

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

• Designing parallel agents for weekly competitive research
• Defining agent roles and information handoffs
• Planning quality checks and cost monitoring

Compares a prototype’s rendered screens with its source design to find differences in typography, spacing, colors, images, and text. Produces prioritized fixes and records visual evidence from follow-up checks before handoff.

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

• Check a prototype against its Figma source before handoff
• Compare an image-based build with the original visual
• Review visual differences across screen sizes and states

Turn an early software idea into a concrete recommendation or implementation plan. Assess whether to build, compare approaches, and define success criteria, constraints, tests, and handoff steps so another engineer or agent can proceed.

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

• Planning a new feature before coding
• Assessing whether a feature is worth building
• Choosing a software architecture

Save an unfinished session as a timestamped Markdown handoff. Capture changed files, decisions and their reasons, current progress, blockers, and ordered next steps so work can resume later or continue in another Claude instance.

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

• Saving unfinished work before ending a session
• Preserving progress before switching tasks
• Recording decisions before context compaction

Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.

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

• Continue ongoing work with a fresh agent
• Focus the next session on a specific task
• Hand off work using references to existing documents

Build a software quality assurance process with structured test cases, execution tracking, bug severity levels, and quality metrics. Includes templates for progress reports and team handoffs, plus prompts for agent-driven test execution.

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

• Setting up a software QA process
• Standardizing test cases and bug reports
• Tracking test progress and release criteria

Simplify code, tests, documentation, and configuration while preserving required behavior. Use it during implementation or before handoff to remove duplication, reuse existing mechanisms, and validate that each remaining part serves a clear purpose.

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

• Remove unnecessary complexity during implementation
• Consolidate working changes after tests pass
• Audit a full branch before handoff

Turn feature requests and conversation context into an implementation plan and handoff document. Review existing code, clarify complex requirements, and organize concrete tasks, affected files, verification steps, assumptions, and risks for review before implementation.

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

• Planning a feature for an existing codebase
• Clarifying requirements for a complex feature
• Defining tasks and checks for a new project

Explores an existing codebase at quick, deep, or architecture-focused levels. Summarizes structure, function calls, and dependencies, then produces documentation or a handoff for implementation without changing the code.

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

• Getting oriented in an unfamiliar codebase
• Understanding how a specific feature works
• Mapping layers and circular dependencies

Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with "verify the Abridge Epic handoff".

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

Prepare and manage durable MEX team handoffs. Use when the user asks to hand work to a person or team, prepare an end-of-session handoff, save what the next engineer needs, create a MEX Relay, take or close a Relay, or explicitly invokes /mex-relay or $mex-relay. Treat Relay as a memory and context baton, not chat, notifications, task assignment, issue tracking, or a Jira replacement; do not activate for ordinary status messages that are not durable handoffs.

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

Generate a co-author / collaborator handoff brief for a multi-author, multi-machine project — summarizing what changed since the last brief (git delta), the current state of each artifact (manuscript, analysis, slides), open questions, how to reproduce locally, and any restricted-data access steps. Use when user says "coauthor brief", "handoff brief", "bring my coauthor up to speed", "what changed since last week", "onboard a collaborator", "write a handoff for [name]", or before sending a co-author the repo. NOT a commit or a checkpoint — it is the cross-machine, cross-person summary `meta-governance.md` only partially covers.

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

Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.

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

Save provenance, decisions, phases, context policy, and next steps as kernel.handoff/v1. Triggers: handoff, save, pause, context, continue later.

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

Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative direction, design-development handoff, QA gate, agent-driven QA, and when a creative-direction project is starting, mid-flight with broken cadence, or integrating AI agents into PM workflow. Does NOT fire for project scoping (use `creative-brief`), aesthetic direction (use `creative-direction`), or general project management without a creative-direction throughline.

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

Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a structured AskUserQuestion multi-option picker for user agency, and dispatches the chosen mode. Mode D (Atlas Fleet) is selectable only when detect_capabilities returns tier=premium (licensed atlas-launcher detected); otherwise it is a locked Atlas Pro teaser. Plan Mode is NOT used (spec section 13.5): AskUserQuestion is the sole user-agency mechanism. Declares HANDOFF complete so EXECUTE can follow.

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

Decompose a session into typed handoff units and recall them later. Use when ending a session or resuming work whose prior state must be recovered.

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

Write the weekly on-call handoff: everything the incoming on-call needs, triage-ready, posted to the channel at shift boundary. Use when the weekly routine fires, or when someone asks for a handoff / shift summary / "catch the next on-call up".

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

Generate a self-contained handoff prompt that lets the user continue work in a fresh coding agent session with empty context. The prompt captures everything a new agent needs: project, goal, progress, decisions, current state, and remaining work. **Triggers — use this skill when:** - User says "handoff", "hand off", "hand-off" - User asks to "generate a continuation prompt" - User says "give me a prompt to continue this" - User asks to "wrap up for a new session" - User says "context transfer", "session transfer" - User asks "how do I pick this up later" - User wants to "pass this to another agent"

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