skills.rest
martin-janci
martin-janciCOMMUNITY
Explore all skills by this author →
GitHub

orchestrator-control-skill

Coordinate PR lifecycles and multi-agent workflows across isolated worktrees.

3|Updated Dec 30, 2025
Search Tags:#automation#multi-agent#orchestrator#git-worktrees#merge-conflicts#pr-lifecycle
One-click install
npx skills add https://github.com/martin-janci/claude-marketplace --skill orchestrator-control-skill-martin-janci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-control-skill
Source: https://github.com/martin-janci/claude-marketplace/tree/main/plugins/bmad-system/skills/orchestrator-control
Command: npx skills add https://github.com/martin-janci/claude-marketplace --skill orchestrator-control-skill-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes control of PR lifecycles and multi-agent coordination to reduce manual overhead and coordination errors.

Core Features & Use Cases

  • Orchestrator control spawns and manages a master control thread and per-PR shepherds.
  • Monitors system health, thread status, and escalations, coordinating sub-agents across worktrees.
  • Handles PR workflows including merge conflicts, review comments, and configurable auto-merge behavior.

Quick Start

Start the orchestrator control to monitor PR lifecycles and coordinate multi-agent workflows.

Frequently Asked Questions about orchestrator-control-skill

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

FAQPage Schema
How do I automate multi-agent coordination for pull request lifecycles?▼

Multi-agent coordination for PR lifecycles is automated by a master orchestrator control thread that spawns per-PR shepherds and sub-agents across isolated git worktrees. This centralizes monitoring and reduces manual coordination overhead.

What is the best way to handle merge conflicts across multiple isolated worktrees?▼

Handling merge conflicts across worktrees is managed by the orchestrator control's per-PR shepherds. These sub-agents monitor PR workflows and escalate issues to the master thread for coordinated conflict resolution.

Do I need a Bash-based control interface to manage thread lifecycles and polling?▼

Yes, a Bash-based control interface is required to operate thread lifecycle management safely. It enables configurable auto-merge and polling behavior for monitoring system health and PR escalations.

Can I configure auto-merge behavior for monitored pull requests?▼

Yes, auto-merge behavior is configurable within the orchestrator control workflow. The master thread monitors PR comments and system health to safely manage automated merging based on your settings.

How does an orchestrator monitor system health and thread status for PR workflows?▼

The orchestrator monitors system health and thread status by coordinating a master control thread with per-PR shepherds. It tracks escalations and manages sub-agents to maintain stable PR workflows.

Related Skills

Explore More Software Engineering Skills→
hanibalskhanibalsk

threads-skill

Coordinate multiple Claude agent threads with isolated git worktrees and event-driven messaging.

Community
Advanced
brujackbrujack
5

babysit

Triage GitHub PR comments, resolve merge conflicts, and stabilize CI failures.

Community
Intermediate
hanibalskhanibalsk

orchestrator-control-skill

Coordinate multi-agent PR lifecycle management across isolated worktrees.

Community
Advanced
hanibalskhanibalsk

thread-orchestrator-skill

Coordinate multiple Claude agent threads with isolated git worktrees.

Community
Advanced