dev-orchestrator
Detect bundled dev work — multiple implementation tasks in one prompt — and dispatch each as an isolated agent (own session, own cwd, scoped tools, awaited), classifying dependencies so independent tasks fan out in parallel and dependent ones run in order. Use when a prompt bundles two or more dev tasks like "generate test cases and create the PR", "bug report and test plan", "do X and Y in parallel", or explicit /orchestrate. Opt into worktree mode via "--worktree" (or "in a worktree", "isolated branch", "auto-merge to main") to provision an integration branch off the protected base (develop/dev preferred; else newer main/master tip), spawn one worktree per task off that branch (parallel for independent, waves for soft-sequenced, merged-into-one for hard-chained), and hand off to agent-pr-creator for the protected-base PR. Resolves issue-tracker tickets (Linear, Jira, GitHub Issues, Notion) via MCP and uses the ticket id as the integration branch name. Skip for single-task asks, questions, or info requests.
The canonical home for this skill is dev-orchestrator in ravnhq/ai-toolkit
Quality
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' must be a string, got object | Fail |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Failed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.