handoff
Generate optimized handoff prompts for delegating work to another LLM agent. Use when handing work to GPT-5.x/Codex, Claude 4.x, Gemini 3.x, or Grok 4.x, either as a shared-workspace sub-task handoff or a fresh-context handoff for a new session or model. Triggers on requests like "create a handoff prompt", "delegate this task to another agent", "hand this off", or "prepare context for another agent".
What this skill does
# Handoff Prompt Generator Generate a prompt that another agent can execute without guessing. ## Choose the handoff mode - Use a shared-workspace handoff when the receiving agent can access the same repo, files, and artifacts. - Use a fresh-context handoff when the receiving agent starts cold, in another session, or on another platform. - Ask for the target model family if it is not implied by the user's request. If it still is not known, draft a vendor-neutral base prompt and mark any missing model-specific adjustments. ## Read one model reference Read only the reference that matches the receiving model: | Target model family | Reference | | --- | --- | | OpenAI GPT-5.x / Codex | [references/openai.md](references/openai.md) | | Anthropic Claude 4.x | [references/anthropic.md](references/anthropic.md) | | Google Gemini 3.x | [references/google.md](references/google.md) | | xAI Grok 4.x / Grok Code | [references/xai.md](references/xai.md) | If the requested model version is newer than the reference, verify the latest official docs before drafting the handoff. ## Gather only execution-critical context Collect the minimum information that removes ambiguity: - objective - success criteria - scope boundaries - relevant files, commands, URLs, or artifacts - current state and known blockers - verification steps - output location or return format - coordination notes for parallel work Do not pad the handoff with background that does not change the receiver's next action. ## Build the base handoff Use flat labeled sections. Prefer direct operational language over narrative explanation. ### Shared-Workspace Handoff ```text Target model: [family/version] Handoff type: shared-workspace sub-task Objective [One concrete outcome] Success criteria - [Observable completion condition] - [Verification condition] Context - [Only facts needed for this slice of work] Inputs and artifacts - [file paths, branches, logs, docs, prior outputs] Ownership - [files or directories to modify] - [areas to avoid] Constraints - [technical limits] - [things the agent must not do] Verification - [commands, tests, or review checks to run] Output - [exact return format] - [where to write or save artifacts] Coordination - [how this work fits with parallel tasks] ``` ### Fresh-Context Handoff ```text Target model: [family/version] Handoff type: fresh context Project - name: [project name] - overview: [1-2 sentences] - entry points: [first files or docs to read] Current state - completed: [what is already done] - remaining: [what still needs to be done] - blockers/baseline: [known failures, risks, or assumptions] Task - objective: [single outcome] - success criteria: - [observable condition] - [verification condition] Constraints - [scope limits] - [things not to change] - [environment or policy constraints] Verification - [commands, tests, or manual checks] Output - [exact deliverable shape] - [how to report open questions or TODOs] ``` Use placeholders like `[TODO: exact path]` instead of inventing repository facts. ## Apply model-specific tuning After drafting the base handoff: - add only the adjustments from the matching reference file - prefer external runtime settings when the receiving harness exposes them - avoid inventing API-only controls inside plain chat prompts - generate one prompt per target model if the user wants multiple versions ## Hold the quality bar - Keep the task atomic. - Define what "done" means. - Name files and commands whenever possible. - Reference shared artifacts by path instead of pasting large logs. - State explicit stop rules for destructive or broad changes. - Ask for findings first for review tasks. - Require source boundaries and citation expectations for research tasks. ## Return format When the user asks for a handoff prompt: 1. Return the ready-to-send prompt in a fenced code block. 2. List assumptions or placeholders after the prompt. 3. Generate separate prompts when the user wants handoffs for multiple models.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.