claude-manager

Track Claude sessions and spawn workers for task coordination.

5|Updated Apr 9, 2018
One-click install
npx skills add https://github.com/angusjfw/hbz --skill claude-manager-angusjfw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-manager
Source: https://github.com/angusjfw/hbz/tree/main/claude/skills/claude-manager
Command: npx skills add https://github.com/angusjfw/hbz --skill claude-manager-angusjfw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The Claude Manager Skill streamlines the management of Claude sessions, tracking multiple sessions, and spawning workers for specific tasks, ensuring a seamless and productive conversation management experience.

Core Features & Use Cases

  • Session Tracking: Keeps a registry of Claude sessions, maintaining context and continuity across sessions.
  • Worker Management: Spawn workers for specific tasks, maintaining separate threads of work within the conversation.
  • Meta-Work Handling: Handles the meta aspects of a conversation, deferring complex tasks to workers.

Quick Start

Activate the claude-manager skill to initiate a new session for managing your Claude conversation.

Frequently Asked Questions about claude-manager

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

FAQPage Schema
How do I manage multiple Claude sessions at the same time?

Managing multiple Claude sessions requires a session registry that tracks active conversations. This maintains context and continuity across separate threads, ensuring seamless coordination without losing track of previous interactions.

How does worker spawning handle complex Claude conversation tasks?

Worker spawning handles complex Claude conversation tasks by deferring them to separate workers. This manages meta-work by maintaining independent threads of execution, keeping the primary conversation focused while background tasks operate.

Do I need a specific Claude environment for session tracking and lifecycle management?

Yes, session tracking and lifecycle management require a Claude environment. This environment supports the underlying session registry, worker spawning, and coordination mechanisms required to maintain conversation continuity.

What is the best way to coordinate separate tasks within a single Claude conversation?

The best way to coordinate separate tasks within a Claude conversation is by spawning dedicated workers. This meta-work handling approach maintains separate threads of work, ensuring specific tasks execute independently while preserving overall session continuity.

When should I use worker spawning instead of keeping everything in one Claude session?

Use worker spawning instead of a single Claude session when handling complex meta-work. Spawning workers maintains separate threads for specific tasks, preventing the primary conversation from becoming overloaded and ensuring better task lifecycle management.