waking-another-session

Name: waking-another-session
Availability: InStock
Author: tuvens

Wake an existing Claude Code session by writing a durable signal file.

Updated Aug 27, 2026

Search Tags:#claude code #cross-session #session orchestration #push notification #sprint coordination #signal file

Ready to run

npx skills add https://github.com/tuvens/phased-development --skill waking-another-session

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: waking-another-session
Source: https://github.com/tuvens/phased-development/tree/main/skills/waking-another-session
Command: npx skills add https://github.com/tuvens/phased-development --skill waking-another-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates handoffs when one already-running Claude Code session needs another session to react to a state change, without starting a new session or losing context.

Core Features & Use Cases

Cross-session wakeups: Triggers an existing target session to respond to allocation, merge approval, blocker escalation, or regression follow-up.
Durable signaling: Writes a signal file that preserves the handoff intent for the target session to read on its next turn.
Fallback delivery: Supports an operator ping-pong path for normal use and a legacy paste-block plus push-notification path when direct operator input is unavailable.
Orchestration fit: Useful for sprint agents, phase leads, and leadership sessions that must coordinate across phases and worktrees.

Quick Start

Ask the AI to wake the named target session by writing the appropriate signal and preparing the correct handoff path for the current coordination scenario.

Frequently Asked Questions about waking-another-session

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

FAQPage Schema

How do I wake a running Claude Code session without spawning a new one?▼

To wake a running Claude Code session without spawning a new one, write a durable cross-session signal file that preserves handoff intent for the target session to read on its next turn. This directs the correct handoff path for sprint and phase coordination.

What is cross-session signal file orchestration used for in Claude Code?▼

Cross-session signal file orchestration coordinates handoffs when one running Claude Code session needs another to react to state changes like slot allocation, merge approval, blocker escalation, or regression follow-up without losing context or starting a new session.

How do I trigger a cross-session handoff for sprint coordination when direct operator input is unavailable?▼

To trigger a cross-session handoff when direct operator input is unavailable, use the legacy paste-block and push-notification fallback path. This delivers the handoff signal to the target session when the default operator ping-pong path is not possible.

Do I need a known remote-control session name to coordinate cross-session wakeups?▼

Yes, cross-session wakeups require a known remote-control session name, a writable status-board path, and support for the ping-pong default or paste-block and push-notification fallback to direct the correct handoff path for leadership coordination.

Can I use cross-session signaling to coordinate merge approvals across multiple worktrees?▼

Yes, cross-session signaling coordinates merge approvals across multiple worktrees and phases. The durable signal file ensures the target leadership or phase lead session reacts to the state change on its next turn without losing existing context.

Why does my Claude Code session wakeup signal fail to trigger a response?▼

A session wakeup signal fails if the writable status-board path is missing, the remote-control session name is unknown, or the operator ping-pong and paste-block fallback paths are unsupported, preventing the target session from reading the handoff intent.