Autonomous Issue Orchestrator FAQs

Question 1

How many tasks can this skill handle simultaneously?

Accepted Answer

By default, it supports up to 5 parallel workers to ensure rapid progress across multiple issues without overwhelming system resources.

Question 2

Does it save progress if the session is interrupted?

Accepted Answer

Yes, all state, worker PIDs, and logs are persisted in a local .orchestrator directory, allowing the workflow to resume exactly where it left off.

Question 3

What happens if an autonomous worker fails to solve an issue?

Accepted Answer

Instead of stopping, the orchestrator triggers a research cycle to investigate logs and documentation, attempting the fix again with new context before marking it as blocked.

Question 4

Is human intervention required during autonomous operation?

Accepted Answer

The skill requires an initial explicit 'PROCEED' confirmation from the user to start, but then manages workers, research cycles, and PRs autonomously until completion or a true blocker is reached.

Question 5

What are the prerequisites for using this skill?

Accepted Answer

You need the GitHub CLI (gh) authenticated, support for Git worktrees, and the worker-dispatch, worker-protocol, and ci-monitor skills installed.

Autonomous Issue Orchestrator

Key Features

Use Cases

Autonomous Issue Orchestrator

Key Features

Use Cases