Plans and dispatches parallel subagent implementation waves from a .planning findings dossier.
npx skills add https://github.com/bravros/bravros --skill orchestrate-bravros
Please help me install this Agent Skill. Skill: orchestrate Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/orchestrate Command: npx skills add https://github.com/bravros/bravros --skill orchestrate-bravros
.planning/P-NNNN-* folder, folds JSONL event logs, cuts units of work, builds dependency graphs, and schedules waves for maximum parallelism. - Tiered subagent dispatch: Assigns haiku/sonnet/opus model tiers per unit, spawns whole waves in one message, and enforces that no two writers touch the same file. - Branch and worktree gating: Refuses to orchestrate product code on the staging or main branch, cutting a feature/ or fix/ branch first. - Use Case: After /recon produces a findings dossier for a multi-repo defect, run /orchestrate .planning/P-0042-skale-replay to have subagents implement all fixes in parallel waves while the orchestrator reviews diffs, commits per phase, and runs final acceptance verification. ## Quick Start Ask the agent to orchestrate the findings dossier at .planning/P-NNNN-slug so it plans the execution waves and dispatches subagents to implement them.High-intent search queries and answers about installing and using this skill.
Run /orchestrate with the dossier folder path, such as /orchestrate .planning/P-0042-skale-replay. The orchestrator reads every file, derives units and parallel waves, writes execution-plan.md, then dispatches subagents to implement each phase.
Each unit gets a marker: [H] for mechanical work runs on haiku, [S] for logic and integrations runs on sonnet, and [O] for architecture runs on opus. The orchestrator sets the model parameter explicitly on every dispatch to match the marker.
No. The skill enforces a branch gate that checks the current branch and worktree status before any edit. If you are on staging, main, or master outside a linked worktree, it cuts a feature/ or fix/ branch from the staging base first.
The orchestrator verifies load-bearing premises against the live code before dispatching anything. Claims tagged READ or ASSUMED get a read-only re-verify unit scheduled ahead of the fix, and a wrong premise stops the run with a report to the operator.
Waves are cut so no two units in a wave share an implicated file, and the whole wave is spawned in one message. Hot files that would serialize everything get an explicit strategy, such as one owner-worker or a split-first unit.
kucherenkoSurvey codebase, tests, dependencies, documentation, and ledger into a reconnaissance dossier.
24601Merge base branch, run tests, bump VERSION, update CHANGELOG, and open a pull request.
gautam-achieveaiImplement approved plans into code using TDD and verification.
m16khbDispatch fresh subagents per task with code review and test gates.