handoff-to-teammate

Route work, create handoff files, and notify recipients in team workflows.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/hilbertp/liberation-of-bajor --skill handoff-to-teammate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-to-teammate
Source: https://github.com/hilbertp/liberation-of-bajor/tree/main/.claude/skills/handoff-to-teammate
Command: npx skills add https://github.com/hilbertp/liberation-of-bajor --skill handoff-to-teammate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In a multi‑role AI‑driven workflow, there is no consistent method to pass work from one role to another, leading to missed steps, duplicated effort, and unclear accountability.

Core Features & Use Cases

  • Structured routing: Determines all required receivers before any artifact is created.
  • Per‑receiver artifacts: Generates a handoff file in each receiver’s inbox with a standardized header.
  • Economics logging: Records a single timesheet entry for the whole session.
  • Anchor stamping: Writes one anchor entry tying together all artifacts and timesheet data.
  • User report: Summarizes recipients and suggests the next context window to open.

Quick Start

Invoke the handoff skill when a role finishes work and needs to pass deliverables to the next role(s).

Frequently Asked Questions about handoff-to-teammate

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

FAQPage Schema
How do I automate role-to-role handoffs in a multi-role AI workflow?

Automating role-to-role handoffs requires routing deliverables to downstream roles by generating standardized handoff files in each receiver's inbox, appending audit logs, and notifying recipients without manual file creation. This ensures consistent passing of work across team workflows.

What is the best way to pass deliverables to multiple downstream roles simultaneously?

Passing deliverables to multiple downstream roles involves structured routing to determine all required receivers first, then creating per-receiver artifacts with standardized headers in each inbox. This prevents missed steps and duplicated effort when a role finishes a task.

How do I log timesheet and audit entries when passing work between team roles?

Logging timesheet and audit entries during work handoffs is done by recording a single session timesheet entry and writing an anchor entry that ties together all generated artifacts and timesheet data for clear accountability.

Does this handoff routing approach work within the Liberation of Bajor system?

This handoff routing approach applies specifically to the Liberation of Bajor system, facilitating role-to-role transitions by writing handoff files, appending anchor entries, and generating user reports to suggest the next context window to open.

Can I generate a user report after routing work to downstream team members?

Generating a user report after routing work is supported natively, summarizing all recipients and suggesting the next context window to open so the user knows exactly which downstream role to transition to.

Why do I need anchor stamping when creating handoff artifacts?

Anchor stamping is needed when creating handoff artifacts to write a single entry tying together all generated artifacts and timesheet data, ensuring clear accountability and traceability across the entire multi-role workflow session.