skills.rest
zts212653
zts212653COMMUNITY
Explore all skills by this author →
GitHub

thread-orchestration

Decomposes large tasks into parallel sub-threads with cat assignment and result aggregation.

2.9k|733|Updated Mar 12, 2026
Search Tags:#task decomposition#multi-agent orchestration#worktree isolation#Code review#reporting contract#thread proposal#parallel threads
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill thread-orchestration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thread-orchestration
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/thread-orchestration
Command: npx skills add https://github.com/zts212653/clowder-ai --skill thread-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large tasks with multiple independent deliverables get stuck in a single conversation thread, forcing serial execution and losing track of who owns what. This Skill orchestrates the full lifecycle of splitting work into parallel sub-threads, assigning the right agents, and aggregating results back to the main thread.

Core Features & Use Cases

  • Task Decomposition & Thread Proposals: Identifies independent deliverable units and creates thread proposals via cat_cafe_propose_thread that require user approval before any thread exists.
  • Reporting Contracts: Configures per-thread reportingMode (final-only, none, state-transitions, blocking-ack) so sub-threads report back with the right cadence and no process noise.
  • Worktree Isolation & Aggregation: Enforces independent git worktrees per thread, serial dependency handling, and a final summary report aggregating all sub-thread outcomes.
  • Use Case: A feature request touches the Web UI, an external API integration, and CI configuration. The Skill splits it into three proposed threads, assigns implementation and review to different cats, runs them in parallel worktrees, and delivers one merged summary to the main thread.

Quick Start

Ask the agent to break this large task into independent sub-tasks and orchestrate them as parallel threads with assigned cats and a final aggregated report.

Frequently Asked Questions about thread-orchestration

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

FAQPage Schema
How do I split a large task into parallel threads?▼

Identify sub-tasks that different agents can complete independently in separate worktrees, then call cat_cafe_propose_thread for each with a title, reason, preferred cats, and projectPath. Threads are only created after the user approves each proposal card.

When should I create a new thread versus posting to an existing one?▼

Always run list_threads first to check for an existing thread covering the topic. If one exists, deliver the information with cross_post_message instead; only propose a new thread when no existing thread owns the scope, since new threads add operator cognitive load.

What is the difference between reportingMode final-only and blocking-ack?▼

final-only (the default) lets the sub-thread work autonomously and report one final summary after completion, with no mid-process messages. blocking-ack makes the sub-thread pause at each blocker, notify the main thread, and wait for acknowledgment before continuing.

Why does cross_post fail right after proposing a thread?▼

cat_cafe_propose_thread returns a proposalId, not a threadId, and the thread does not exist until the user approves the proposal card. Wait for the approval event before sending the first message, which must include a main thread ID header.

Can the same agent implement and review a sub-task?▼

No. The skill enforces a no self-review rule: implementation and review of the same sub-task must be assigned to different cats, ideally across families, to keep review independent.

When should I not use thread orchestration?▼

Skip it for single tasks done directly, passive coordination between existing threads (use cross-thread-sync), subagent parallelism inside one session (a CLI built-in), or splitting so finely that orchestration overhead exceeds the benefit.

Related Skills

Explore More Software Engineering Skills→
dmooneydmooney

backlog

Organizes GitHub issue backlog via triage, fix-one, and drain modes.

Community
Advanced
Zhijiang-Li1111Zhijiang-Li1111
10

finishing-branch

Automate stakeholder review and approval before merging completed software.

Community
Intermediate
zts212653zts212653
2.6k

cross-thread-sync

Coordinate parallel sessions across threads with a 3+2 notification protocol.

Community
Advanced
erikstmartinerikstmartin
16

subagent-driven-development

Spawn fresh subagents to execute independent tasks in parallel within a session.

Community
Advanced