multi-session

Coordinate concurrent AI coding sessions with locks, heartbeats, and merge workflows.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill multi-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-session
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/multi-session
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill multi-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates safe, conflict-free collaboration across multiple AI coding sessions by providing explicit locks, heartbeats, and merge workflows to prevent overlapping edits.

Core Features & Use Cases

  • Session locks to claim PRDs and prevent concurrent edits.
  • Heartbeat tracking to detect stale work and keep sessions alive.
  • Merge-ready workflow with a structured path from claim to completion.
  • Use Case: Teams coordinate parallel work on the same codebase without conflicts, across PRDs.

Quick Start

Enable multi-session mode in your project.json, then start a session to claim a PRD, work on its stories, and update heartbeats.

Frequently Asked Questions about multi-session

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

FAQPage Schema
How do I prevent conflicts when multiple AI coding sessions edit the same codebase?▼

To prevent conflicts when multiple AI coding sessions edit the same codebase, you use explicit session locks to claim PRDs and block overlapping concurrent edits. This lock-based coordination enables safe parallel development.

How does heartbeat tracking detect stale work in parallel development workflows?▼

Heartbeat tracking detects stale work by monitoring per-session heartbeat signals to maintain active status. If a session stops updating its heartbeat, the workflow flags that branch as stale, keeping the merge-ready path safe.

Can I use multi-session to coordinate parallel work across different git branches?▼

Yes, you can coordinate parallel work across different git branches. The workflow requires per-session heartbeats, PRD registry updates, and safe commit practices to ensure branches remain merge-ready throughout development.

What's the best way to claim a PRD for a concurrent AI coding session?▼

The best way to claim a PRD for a concurrent AI coding session is to enable multi-session mode in your project.json, then start a session to claim the PRD, work on its stories, and continuously update heartbeats to maintain the lock.

Do I need autoCommit configured to safely merge parallel AI coding branches?▼

When autoCommit is configured, you need governance around safe commit practices to safely merge parallel AI coding branches. This ensures the structured path from claim to completion avoids conflicts during the merge process.

When should I not use session locks for collaborative development workflows?▼

You should avoid session locks for collaborative development workflows when your project lacks PRD-based work or does not require per-session heartbeats. Without governance around session locks and registry updates, the merge-ready workflow cannot function properly.