gxpm-handoff

Generate a structured handoff document with phase and provenance metadata.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gxpm-handoff
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-handoff
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compact the current session into a handoff document so another agent can continue the work without context loss.

Core Features & Use Cases

  • Gather essential context (phase, blockers, decisions, next steps) and preserve it in a formal handoff.
  • Produce a phase-handoff artifact that links to key plans, ADRs, and test results to enable rapid resumption.
  • Trigger handoffs at session end, agent switch, or when transferring work between implementer subagents.

Quick Start

Trigger a handoff by generating a phase-handoff artifact for the next agent.

Frequently Asked Questions about gxpm-handoff

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

FAQPage Schema
How do I create a handoff document for another AI agent?

To create a handoff document, you compact the current session into a structured artifact capturing phase, blockers, decisions, and next steps. This preserves essential context so another agent can continue the work without loss.

What is a session handoff artifact and when do I need one?

A session handoff artifact is a structured document that captures essential context like phase and blockers. You need one when ending a session, switching agents, or passing work between implementer subagents to prevent context loss.

How do I transfer context between agents without losing session history?

You transfer context by compressing the current session into a formal handoff document. This artifact links to key plans, ADRs, and test results, enabling rapid resumption for the next agent without duplicating content.

Does this handoff workflow capture phase metadata and provenance?

Yes, the handoff workflow generates a structured artifact with target phase metadata and provenance. It explicitly captures the current phase, blockers, decisions, and next steps to ensure seamless work continuation.

What is the best way to pass work between implementer subagents?

The best way to pass work between implementer subagents is generating a phase-handoff artifact. It compiles essential context and references relevant plans and test results, allowing the next subagent to resume work rapidly.

When should I avoid using a session handoff document?

You should avoid generating a handoff document if the session lacks meaningful progress or unresolved blockers. The artifact is designed to capture actionable phase metadata and next steps, avoiding unnecessary content duplication.