skills.rest
sarkarshivaditya-lab
sarkarshivaditya-labCOMMUNITY
Explore all skills by this author →
GitHub

autonomous-orchestration

Orchestrates parallel background workers across GitHub issues until scope completion.

Updated Jan 1, 2026
Search Tags:#automation#github#orchestration#issue tracking#project board#ci monitoring#parallel workers
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill autonomous-orchestration-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autonomous-orchestration
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/autonomous-orchestration
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill autonomous-orchestration-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating work across many GitHub issues manually requires constant supervision, context switching, and repeated status checks. This Skill runs an autonomous orchestration loop that dispatches parallel worker agents, monitors their progress, merges passing PRs, and continues until every issue in scope is complete—without user intervention. ## Core Features & Use Cases - Parallel Worker Dispatch: Spawns up to 5 background worker agents concurrently using the Task tool and monitors them with TaskOutput. - GitHub-Centric State Management: Uses the GitHub Project Board as the source of truth, with issue comments as activity logs and MCP Memory markers to survive context compaction. - PR Resolution Bootstrap: Resolves all existing open PRs (checking CI status and review artifacts) before spawning new workers, and merges green PRs immediately each loop. - Failure Recovery: Runs up to 3 research cycles per failed issue before marking it blocked, with SLEEP/WAKE handling when only CI waits remain. - Use Case: Point it at a milestone or epic (e.g., "work through all issues in milestone v1.0.0") and it will autonomously assign workers, review PRs, merge passing changes, and report status to a tracking issue until the milestone is done. ## Quick Start Ask the AI to autonomously work through all open issues in a specific milestone or epic using the autonomous-orchestration skill.

Frequently Asked Questions about autonomous-orchestration

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

FAQPage Schema
How do I run autonomous work across multiple GitHub issues?▼

Request autonomous operation with a scope such as a milestone, epic label, or all open issues. The orchestrator spawns up to 5 parallel background workers via the Task tool, monitors them with TaskOutput, and loops until no open issues or PRs remain.

How does the orchestrator track worker and issue state?▼

The GitHub Project Board Status field is the single source of truth, with issue comments as the activity log. Labels only track lineage, and an MCP Memory ActiveOrchestration marker lets a new session detect and resume orchestration after context compaction.

What happens when a worker fails on an issue?▼

Failed workers trigger research cycles with read-only research agents that document findings on the issue. Only after 3 or more research cycles conclude the issue is impossible without external input is it marked Blocked on the project board.

Does the orchestrator merge pull requests automatically?▼

Yes. Every loop iteration merges any PR whose CI checks all pass and whose linked issue has a completed review artifact, unless it carries a do-not-merge or release-placeholder label. It never waits for user confirmation to merge green PRs.

What are the prerequisites for autonomous orchestration?▼

You need an authenticated GitHub CLI, a configured GitHub Project Board with a Status field, a tracking issue labeled orchestration-tracking, and the companion skills worker-dispatch, worker-protocol, and ci-monitoring.

When does autonomous orchestration stop or sleep?▼

It exits only when no open issues, in-progress work, or open PRs remain in scope. It enters SLEEP when all remaining work is blocked or waiting on CI, posting state to the tracking issue so a SessionStart hook or manual resume can wake it.

Related Skills

Explore More Software Engineering Skills→
AutumnsGroveAutumnsGrove
5

badger-triage

Organize GitHub project board issues by assigning sizes, priorities, and milestones.

Community
Advanced
joi-fairsharejoi-fairshare
1

addressReview

Merge human PR feedback with structured issues and coordinate parallel implementation agents.

Community
Advanced
o9nno9nn

prcheckloop

Monitor GitHub PR checks, diagnose failures, and push corrective commits.

Official
Intermediate
albertdobmeyeralbertdobmeyer
2

coding-agent

Launch coding agents in background processes with isolated workdirs and monitoring.

Community
Advanced