handoff

Transfer ongoing work with decisions, evidence and actionable next steps. Triggers on "handoff", "交接".

SKILL.md

GitHub

Handoff

When to use

  • Transfer ongoing work with decisions, evidence and actionable next steps.

Not for: context-engineering for explanations or new-task context.

Steps

  1. Read current goal, artifacts, diff and check state; preserve decisions and questions.

  2. Summarize completion, failures and reasons for consequential decisions, linking existing artifacts.

  3. Provide next steps, commands, boundaries and environment limits; redact secrets and separate facts from hypotheses.

  4. Deliver in conversation or an approved path; start or message other sessions only with explicit authorization and supported tools.

Verify

  • A new session can resume concretely; no secrets, invented approvals or unsupported background commands appear.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • references/on-call-shift.md — on-call shift handoff: active incidents, in-progress investigations, recent changes, known issues, escalation triggers, pre/mid/post-shift checklist