Individual skill

workflow-threads-manager

Oversee the other Claude threads (sessions) working on the same project. Check what each is doing, confirm finished work is merged to main, has its changelog entry with screenshots, and is live, archive threads that are truly done, and restart or flag threads that were cut off. Use when the user says "check threads", "check new changes", "are the threads merged and pushed", "archive the done threads", or asks what the other sessions are up to. Project specifics (changelog format, live site, capture folders) go in an optional local references/<project>.md next to this skill.

agent-skills/workflow/workflow-threads-manager/SKILL.md

Read pinned source

Source commit 5ea1661a0e05d82b054553daaa6baf6d0233c33c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
7,316
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Workflow: threads manager

The user runs many Claude threads at once on one repository, and asks this thread to keep track of them. Each check answers four questions:

1. **What landed on `main`** since the last check, and does every change have its changelog entry with its pictures?
2. **Is live healthy and current**, or is it broken or behind `main`?
3. **What is each thread doing**: running, finished, cut off mid-task, or waiting on the user?
4. **What can be archived**, and what needs the user?

If this skill has a `references/<project>.md` for the current project, read it. Read the project's `AGENTS.md` first on every check, because other threads keep changing the rules (the live host, the changelog format, the size limits). Where `AGENTS.md` and this skill disagree, `AGENTS.md` wins.

## Tools

- **Session tools** (`mcp__ccd_session_mgmt__*`). If any of these show up only as deferred tool names, load them with ToolSearch first.