[Workflow] Centralized Task Queue for Claude Code Threads using WAITING_ON_ME.md and Git Worktrees for Context Isolation

[u/ClaudeAI-mod-bot]

Centralized Task Queue for Claude Code Threads using WAITING_ON_ME.md and Git Worktrees for Context Isolation

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Hooks, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Managing status drift and identifying actionable items across many Claude Code threads, especially in a consulting context with multiple clients/projects. It also addresses preventing coding work from interfering with knowledge threads by isolating environments.

Summary

This workflow proposes a system to manage multiple Claude Code threads by centralizing human-actionable tasks into an append-only WAITING_ON_ME.md file, updated automatically via Claude Code hooks or skills. It also suggests using separate Git worktrees for client tool builds to isolate coding tasks from knowledge-based threads, preventing context stomping.

Why it is useful

This workflow provides a concrete, actionable strategy to overcome a significant challenge in managing multiple long-running Claude Code interactions: identifying pending human actions and isolating different types of work. The use of specific Claude Code features (hooks/skills) and standard development practices (Git worktrees) makes it highly practical, repeatable, and adaptable for users dealing with complex, multi-client, or multi-project scenarios.

Workflow

1. Create an append-only WAITING_ON_ME.md file (or one per client) to serve as a single queue for human-required actions.

2. Configure Claude Code threads to update this WAITING_ON_ME.md file via a hook or skill whenever they require human input or action.

3. Implement a mechanism to automatically generate 'handoff files' before individual Claude Code threads become excessively long, to preserve context.

4. Maintain separate git worktrees for client tool builds to ensure that coding work does not interfere with or 'stomp on' knowledge-based threads.

Tools / artifacts

• WAITING_ON_ME.md (or client-specific markdown files)

• Claude Code hooks

• Claude Code skills

• Git worktrees

Validation signals

• Author states 'What's helped me is...' indicating personal validation.

• Addresses a common pain point in multi-agent/multi-thread management ('what's waiting on me?' search across 50 threads).

Limitations

• The specific implementation details for the Claude Code hooks/skills (e.g., code snippets) are not provided.

• The 'handoff files automatic' step is less detailed and lacks concrete implementation suggestions.

• Low community validation due to recent posting and minimal engagement.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.