// Standardize coding handoffs between builder, QA, and deploy agents. Use when a coding task moves across stages and requires strict ACK/DONE/BLOCKED status updates, branch metadata, and PR readiness checks.
| name | coding-handoff |
| description | Standardize coding handoffs between builder, QA, and deploy agents. Use when a coding task moves across stages and requires strict ACK/DONE/BLOCKED status updates, branch metadata, and PR readiness checks. |
| version | 1.0.0 |
Copy to agents/<coder>/skills/coding-handoff/SKILL.md. Requires agents configured with sessions_send for inter-agent handoffs.
Always send handoff messages using:
fromtotask_idpriority (P1/P2/P3)summarycontext (branch, commit, environment)done_when (checklist)deliver_to (topic/channel target)ACK quickly with ownership and ETA.DONE with evidence (tests, logs, diff summary) or BLOCKED with explicit unblock requirements.Before DONE, verify:
If any gate fails, return BLOCKED, not DONE.
Branches created during a coding handoff should encode origin and task for traceability:
<agent-id>/<task_id>-<short-slug>
Examples: coder/build-142-coupon-rounding, coder/auth-jwt-001-refresh-token.
This pattern makes it easy to grep history for an agent's work, link branches back to task IDs in topic messages, and reason about cleanup. Avoid bare slugs (fix-bug) or timestamp-only branches — they don't carry provenance.
Do not commit or push unless the task explicitly asks for it. The DONE message references the local branch; pushing/PR-opening is a separate explicit step.
A handoff is bounded by done_when. Anything outside that scope:
Risks/Notes. Do not fix it in the same change.Scope creep turns a 1-hour handoff into a 6-hour mystery. The handoff format exists to keep work bounded — respect it.
Audit SOUL.md, SKILL.md, IDENTITY.md, and workspace templates for frontmatter compliance, duplicate names across core/extended catalogs, description quality, placeholder hygiene, and prompt-budget size before they are copied into an OpenClaw workspace.
Manage ACPX sessions for delegating tasks from an orchestrator agent to coding agents. Use for agent-to-coding-agent work delegation with named sessions, parallel workstreams, and status tracking.
Transform one source artifact into channel-specific drafts while preserving core thesis. Use for cross-post workflows (X, LinkedIn, Reddit, newsletter snippets).
Qualify leads against ICP with transparent scoring and clear next steps. Use when converting raw prospects into prioritized outreach queues.
Triage operational inputs (email, calendar, tasks) into prioritized action queues with explicit ownership and deadlines.
Produce concise, decision-ready market intelligence briefs with confidence and source quality scoring. Use for competitor analysis, trend detection, and strategic signal synthesis.