baton

Archive worktrees into git-tracked tar.gz files with standardized handoff templates.

3|2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/yoonhwan/ai-feature-pack --skill baton-yoonhwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baton
Source: https://github.com/yoonhwan/ai-feature-pack/tree/main/feature-pack/baton/claude-code/skills/baton
Command: npx skills add https://github.com/yoonhwan/ai-feature-pack --skill baton-yoonhwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents often lose critical task context when switching between isolated worktree branches or resuming paused sessions, leading to repeated work, misaligned handoffs, and inconsistent workflow execution across team members and agent platforms.

Core Features & Use Cases

  • Isolated Worktree Management: Automatically creates branch-specific isolated environments with auto port allocation and symbolic link management to prevent code conflicts between parallel feature development.
  • Automated Archive & Handoff System: Compresses completed worktrees into git-tracked tar.gz archives and maintains 4 standardized handoff templates (PLAN/JOURNAL/CURRENT/NEXT) to preserve full session context across agent restarts and team handoffs.
  • Flexible Trigger System: Activates instantly via /baton:* slash commands or natural resume keywords like 이어서, go, continue to resume paused work without manual context setup. For example, when resuming work on a feature branch after a break, simply say 이어서 to automatically load your next steps and continue exactly where you left off.

Quick Start

To resume your paused work immediately, say 이어서 or use the /baton:resume slash command to load your next steps and continue your current task without manual context setup.

Frequently Asked Questions about baton

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

FAQPage Schema
How do I resume paused AI agent tasks without losing session context?

Resuming paused AI agent tasks without losing session context is handled by standardized 4-template handoff protocols (PLAN/JOURNAL/CURRENT/NEXT). Triggering resume via slash commands or natural keywords automatically loads your previous steps and continues exactly where you left off.

How does worktree branch isolation prevent code conflicts during parallel feature development?

Worktree branch isolation prevents code conflicts during parallel feature development by automatically creating branch-specific environments with auto port allocation and symbolic link management. This strict isolation ensures that concurrent AI agent sessions do not overwrite each other's code.

Can I use session handoff workflows across different AI coding environments like Claude Code, Codex, and Gemini?

Session handoff workflows support cross-agent task handoffs across Claude Code, Codex, and Gemini environments. Standardized templates maintain consistent task state, ensuring seamless agent handoffs and workflow execution regardless of the specific AI coding platform used.

What is the best way to archive completed git worktrees?

The best way to archive completed git worktrees is through automated git-tracked tar.gz compression. This archive management system preserves full session context and prevents fragmented workflows when switching branches or concluding feature development.

Do I need manual context setup to switch between worktree branches in AI coding?

No manual context setup is required to switch between worktree branches in AI coding. Flexible trigger systems activate instantly via slash commands or natural resume keywords like continue or go, automatically loading your next steps.

Why does AI agent context get lost when switching between isolated worktree branches?

AI agent context gets lost when switching between isolated worktree branches due to fragmented agent workflows and lack of standardized session handoff protocols. Without automated archive management and strict isolation rules, resuming paused tasks leads to repeated work and misaligned handoffs.