skills.rest
seanspiesman
seanspiesmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

collaboration-tracking

Maintain shared CLI context and log agent handoffs in VS Code Copilot workflows.

Updated Jan 12, 2026
Search Tags:#collaboration#logging#cli#handoffs#agent-workflow#context-sharing
One-click install
npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill collaboration-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: collaboration-tracking
Source: https://github.com/seanspiesman/Agents-and-Workflows/tree/main/custom-agents/skills/collaboration-tracking
Command: npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill collaboration-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that all agents share a common CLI context and log their handoffs to maintain a clear chain of custody.

Core Features & Use Cases

  • Global CLI context awareness: keep a shared reference file at agent-output/cli.md.
  • Handoff logging: append relevant CLI output and decisions to the shared log to preserve traceability.
  • Deprecated logging: Logging to agent-output/logs/ is no longer required as RAG captures context.

Quick Start

Open agent-output/cli.md and append any relevant CLI output or context to maintain a shared language of handoffs across agents.

Frequently Asked Questions about collaboration-tracking

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

FAQPage Schema
How do I keep CLI context in sync across multiple AI agents?▼

To keep CLI context in sync across multiple agents, maintain a shared reference file at agent-output/cli.md where all agents append relevant CLI output and decisions to preserve traceability.

What is agent handoff logging in multi-agent workflows?▼

Agent handoff logging records relevant CLI output and decisions to a shared log, creating a clear chain of custody for multi-agent collaboration workflows in VS Code Copilot environments.

How do I set up context sharing for VS Code Copilot agent workflows?▼

Set up context sharing by opening agent-output/cli.md and appending relevant CLI output or context to maintain a shared language of handoffs across agents in VS Code Copilot.

Do I need to log agent output to agent-output/logs/ for context retrieval?▼

You do not need to log agent output to agent-output/logs/ because logging to that directory is deprecated, as current RAG context features automatically capture the necessary context.

Can I use a shared CLI context file for multi-agent collaboration in VS Code?▼

Yes, you can use a shared CLI context file at agent-output/cli.md for multi-agent collaboration in VS Code Copilot, ensuring shared instructions and consistent context across sessions and handoffs.

Why does my agent workflow lose context during CLI handoffs?▼

Agent workflows lose context during CLI handoffs when agents do not read and update the shared agent-output/cli.md file, which is required for aligning with current RAG context features and maintaining shared instructions.

Related Skills

Explore More Content & Communication Skills→
maestria-comaestria-co

initialize-workspace

Bootstrap per-project agent context across a VS Code multi-root workspace.

Official
Advanced
stephendorstephendor
1

source-command-apm-7-handoff-worker

Create Handoff Logs and Handoff Prompts for APM Worker context handoffs.

Community
Advanced
drvossdrvoss
42

ide-switching

Coordinate Copilot context between VS Code and the Copilot CLI across IDE-to-terminal workflows.

Community
Intermediate
wormholecowboywormholecowboy
1

stateCreate

Create timestamped session state files in a .state directory.

Community
Basic