skills.rest
tlapidus-rgb
tlapidus-rgbCOMMUNITY
Explore all skills by this author →
GitHub

handoff-claude-to-claude

Formalize cross-domain handoffs between Claude VM and Claude Product with metadata and backlog artifacts.

Updated Mar 11, 2026
Search Tags:#workflow#documentation#claude#handoff#traceability#product#vm
One-click install
npx skills add https://github.com/tlapidus-rgb/nitrosales --skill handoff-claude-to-claude
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-claude-to-claude
Source: https://github.com/tlapidus-rgb/nitrosales/tree/main/CLAUDE_VM/SKILLS_VM/skills/handoff-claude-to-claude
Command: npx skills add https://github.com/tlapidus-rgb/nitrosales --skill handoff-claude-to-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes cross-domain handoffs between Claude VM and Claude Product to prevent context loss and ensure proper archival and traceability.

Core Features & Use Cases

  • Defines explicit handoff briefs and mandatory artifacts (BACKLOG_PENDIENTES.md, CLAUDE_STATE_VM.md, and shared handoff folder).
  • Enforces domain separation and idempotent archiving to avoid context leakage.
  • Applies to VM→Product, Product→VM, and coordinated handoffs triggered by sales/marketing tasks, product changes, or Tomy escalations.

Quick Start

Create the handoff brief using the template and save it to BACKLOG_PENDIENTES.md.

Frequently Asked Questions about handoff-claude-to-claude

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

FAQPage Schema
How do I prevent context loss during cross-domain handoffs between Claude VM and Product?▼

To prevent context loss during cross-domain handoffs, formalize the transfer using explicit handoff briefs and mandatory artifacts like BACKLOG_PENDIENTES.md and CLAUDE_STATE_VM.md to ensure proper archival and traceability.

What is the best way to document Claude VM to Product handoffs for traceability?▼

Documenting Claude VM to Product handoffs requires saving explicit briefs into a shared handoff folder and updating BACKLOG_PENDIENTES.md, enforcing domain separation and idempotent archiving for full traceability.

Do I need specific files to formalize a Claude Product handoff?▼

Yes, formalizing a Claude Product handoff requires mandatory artifacts including BACKLOG_PENDIENTES.md, CLAUDE_STATE_VM.md, and a shared handoff folder to maintain provenance and prevent context loss.

Why does idempotent archiving matter for Claude VM and Product workflow transitions?▼

Idempotent archiving matters for workflow transitions because it enforces domain separation and prevents duplicate or conflicting context updates during cross-domain handoffs between Claude VM and Claude Product.

How do I start a handoff brief for a Claude VM escalation?▼

To start a handoff brief for a Claude VM escalation, create the brief using the standard template and save it directly to BACKLOG_PENDIENTES.md to formalize the transfer.

Related Skills

Explore More Content & Communication Skills→
vincent119vincent119

go-ddd

Define Go project architecture with Domain-Driven Design layers and bounded contexts.

Community
Advanced
wonder-zhangwonder-zhang
1

iterate

Generate versioned delta changes from archived feature specs.

Community
Advanced
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
SensLiaoSensLiao

gsd-complete-milestone

Archive project milestones and update tracking documentation with Git tags.

Community
Intermediate