handoff-reply

Read handoff-chat messages and pause for user confirmation before appending replies.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill handoff-reply
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-reply
Source: https://github.com/Levezze/devkit/tree/main/skills/handoff-reply
Command: npx skills add https://github.com/Levezze/devkit --skill handoff-reply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents cross-agent chats from silently bypassing the human by pausing before writing any message that requires the user’s judgment.

Core Features & Use Cases

  • User-first “grill-me” gate: Detects when incoming agent messages require decisions, assumptions, or tradeoffs only the user can own, then asks targeted questions before any reply is appended.
  • Automated chat targeting: Reads the right /tmp/handoff-chat-<slug>.md by slug (or auto-selects the most relevant file when omitted) and identifies the correct participant handle to determine what’s “new.”
  • Draft-before-commit workflow: Produces a structured draft reply for review and confirmation, and only appends it after explicit user approval.
  • Use Case: When another agent proposes a product direction, naming, or “should we ship” decision, the skill ensures the human is asked first with a short, decision-focused set of questions.

Quick Start

Invoke the skill as /handoff-reply to review the newest handoff chat message that needs your judgment, answer the grill questions, and then confirm the drafted reply to post.

Frequently Asked Questions about handoff-reply

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent cross-agent chats from auto-replying without human approval?▼

Human-in-the-loop reply orchestration pauses cross-agent chats before writing messages that require user judgment, parsing chat participants and message history to detect ambiguous or assumption-heavy requests that must not be auto-replied.

How do I implement a draft-before-commit workflow for agent-to-agent coordination?▼

Draft-before-commit workflow for agent collaboration generates a structured draft reply for review, asking targeted grill-me questions first, and only appends the final message to the handoff chat after explicit user confirmation.

What is a grill-me prompt in human-in-the-loop agent collaboration?▼

A grill-me prompt in agent collaboration is a decision-focused gate that detects incoming agent messages requiring tradeoffs or assumptions, then asks the user targeted questions before any reply is drafted and appended to the chat.

Can I auto-resolve handoff chat files when the slug is omitted?▼

Yes, handoff-chat targeting auto-selects the most relevant /tmp/handoff-chat-<slug>.md file when the slug is omitted, reading the correct file and identifying the appropriate participant handle to determine new messages.

When do I need human-in-the-loop guardrails for agent workflow routing?▼

Human-in-the-loop guardrails are needed whenever another agent proposes product directions, naming, or ship decisions, ensuring the human is asked first with a short, decision-focused set of questions before appending any reply.

What are the limitations of chat routing for draft approval in agent coordination?▼

Chat routing for draft approval requires parsing message history and participant handles from /tmp files, meaning it cannot process chats lacking structured handoff files or auto-reply to messages that explicitly require user judgment.