arbe-orchestrate

Triages backlogs and design docs into dependency-wired dispatch plans for delegated workers.

Updated May 16, 2026
One-click install
npx skills add https://github.com/oskarrough/robots --skill arbe-orchestrate-oskarrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbe-orchestrate
Source: https://github.com/oskarrough/robots/tree/main/skills/orchestrate
Command: npx skills add https://github.com/oskarrough/robots --skill arbe-orchestrate-oskarrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs, bug reports, and design docs pile up as vague, duplicated, or stale work items that nobody can safely hand to a builder. This Skill turns that raw input into a reviewed dispatch plan — each task scoped, deduplicated, dependency-wired, and ordered — so a human can approve handoffs in minutes instead of re-triaging everything themselves. ## Core Features & Use Cases - One-at-a-time triage: Surfaces each finding as a single decision with a concrete recommendation, keeping open questions tracked until answered or explicitly parked. - Tracker verification: Checks task statuses against actual repository history, matching commits by meaning rather than by task-id grep, so stale or already-shipped work is caught. - Dependency mapping and dispatch ordering: Reads every task in the set, flags duplicates, cycles, file conflicts, and vague descriptions, then recommends what runs in parallel versus sequentially. - Use Case: Point it at a design doc for a half-built feature. It compares the doc against code and existing tasks, reports whether the doc is fully, partly, or not yet decomposed, and drafts actionable tasks for the remainder — ready for arbe-delegate to launch builders once approved. ## Quick Start Ask the agent to triage the open backlog for a feature area and hand back a dispatch order with dependencies wired.

Frequently Asked Questions about arbe-orchestrate

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

FAQPage Schema
How do I triage a backlog before handing tasks to AI agents?▼

Pull the open tasks for the area, verify each status against recent commit history, then surface issues one at a time — duplicates, vague descriptions, file conflicts, missing dependencies. Finish with a dispatch order showing what runs in parallel versus sequentially.

How do I turn a design doc into actionable tasks?▼

Compare the doc against the code and existing tasks to determine whether it is fully, partly, or not yet decomposed. With approval, write each task as framing and goal — what is wrong, what done looks like, roughly where it lives — never a prescribed solution.

Should a triage agent write code or fix reported bugs?▼

No. A reported bug is a task to file, not a problem to solve. The orchestrator checks the backlog for existing coverage, drafts a two-to-three-line task body if none exists, and leaves diagnosis and implementation to the builder agent.

How do I check if tracker tasks are already done?▼

Treat each status as a claim, not a fact. Have a subagent pull a day of commit subjects across the area and match by meaning, since commit messages describe what changed rather than citing task ids. Check close_reason on anything already closed.

When should a task not be delegated to a worker agent?▼

Skip delegation when the task is a one-file edit you already understand — briefing a worker costs more than doing it directly. Also hold tasks with unresolved dependencies, vague done-criteria, or file conflicts with other tasks in the same batch.