thrum

Route user intents to appropriate thrum-* command skills across worktrees.

28|5|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonletto/thrum --skill thrum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thrum
Source: https://github.com/leonletto/thrum/tree/main/codex-plugin/skills/thrum
Command: npx skills add https://github.com/leonletto/thrum --skill thrum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thrum coordinates multi-agent workflows, messaging, and session context across worktrees and agents to keep coordination explicit and resilient.

Core Features & Use Cases

  • Unified coordination and message routing across agents, worktrees, and sessions.
  • Decision-making to route requests to the appropriate thrum-* command skill and prime context.
  • Cross-worktree synchronization and identity management for multi-agent projects.

Quick Start

Prime your session to initialize context and let Thrum route the request to the appropriate thrum- command.

Frequently Asked Questions about thrum

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

FAQPage Schema
How do I coordinate messages across multiple agents in different worktrees?

Multi-agent message coordination across worktrees is handled by routing user intents to command skills and priming session context to maintain synchronized state. This ensures messaging and coordination remain explicit and resilient across agents.

What is multi-agent workflow coordination and when do I need it?

Multi-agent workflow coordination synchronizes session context and routes messages across agents and worktrees. You need it when managing cross-worktree projects where multiple agents must maintain synchronized state and explicit coordination.

How do I start routing user intents to manage multi-agent sessions?

Start routing user intents by priming your session to initialize context, which lets the system route the request to the appropriate command skill and maintain synchronized state across worktrees and agents automatically.

Do I need a specific file structure to manage multi-agent context routing?

You need a SKILL.md frontmatter at the skill root with a name and description. You may also include optional directories like scripts, references, and assets that are loaded as needed for context routing.

What's the best way to synchronize state across agents and worktrees?

The best way to synchronize state across agents and worktrees is using a coordination layer that routes intents to command skills, primes context, and maintains synchronized state for cross-worktree identity management.