Coding Handoff
Productivitycoding-handoffCoding Handoff is an Agent Skill for productivity published in the raulvidis/openclaw-multi-agent-kit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/raulvidis/openclaw-multi-agent-kit/blob/HEAD/templates/skills/coding-handoff/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/coding-handoff, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Install
Copy to agents/<coder>/skills/coding-handoff/SKILL.md. Requires agents configured with sessions_send for inter-agent handoffs.
Coding Handoff Skill
Required Handoff Envelope
Always send handoff messages using:
fromtotask_idpriority(P1/P2/P3)summarycontext(branch, commit, environment)done_when(checklist)deliver_to(topic/channel target)
Lifecycle
- Post
ACKquickly with ownership and ETA. - Execute scoped checks.
- Post
DONEwith evidence (tests, logs, diff summary) orBLOCKEDwith explicit unblock requirements.
PR Readiness Gate
Before DONE, verify:
- lint/type/test status
- regression risk notes
- rollback note
- unresolved TODOs list
If any gate fails, return BLOCKED, not DONE.
Branch Naming
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.
Scope Discipline
A handoff is bounded by done_when. Anything outside that scope:
- Unrelated bug spotted while working: mention it in the DONE message under
Risks/Notes. Do not fix it in the same change. - Adjacent refactor that "would be nice": skip. File a follow-up task instead.
- Test that fails for unrelated reasons: flag it, route around it, don't paper over it.
Scope creep turns a 1-hour handoff into a 6-hour mystery. The handoff format exists to keep work bounded — respect it.