BMAD Planning Orchestrator plugin
A Claude Code plugin with 20 BMAD method skills: takes a project from brief to stories and splits the work into conflict-free parallel waves
- 493 ★ on the repository
- Last commit
Extended access
Why this level
- The plugin's hooks and shell scripts run inside your project and nudge the next step
- The skills create and edit planning files: PRD, architecture, stories and the manifest
- Planning subagents get access to the project files
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/bmad-planning-orchestratorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin's hooks and shell scripts run inside your project and nudge the next step
- The skills create and edit planning files: PRD, architecture, stories and the manifest
- Planning subagents get access to the project files
This is third-party code. Review the repository files before installing.
What it does
The plugin carries a project through four phases of the BMAD method (Breakthrough Method for Agile AI-Driven Development): analysis, planning, solutioning and handoff to implementation. The scope of work is tuned by a track chosen interactively: Quick Flow, BMad Method or Enterprise. The output is a story file in ready-for-dev status and a tool-agnostic `handoff-manifest.json`. The plugin writes no code; the author leaves implementation to separate tools. It contains 20 skills, among them `bmad-product-brief`, `bmad-prd`, `bmad-architecture`, `bmad-epics-and-stories`, `bmad-readiness-check` and `bmad-sprint-planning`. The author's central contribution is safe parallel development. One architecture prevents semantic conflicts such as differing API styles and data models, and stories are tied to disjoint files and ordered into waves by dependency. The `bmad-parallel-plan` skill builds a dependency graph, splits stories into waves capped by `maxParallel` and writes `parallelization-plan.md` with git worktree branch names and a merge order. Three subagents (epic-scoper, readiness-auditor, story-author) and hooks with next-step nudges come with the plugin.
Who it is for. Team leads and solo developers who plan large work in Claude Code and want to hand independent stories to several agents without merge conflicts.
Good fit when
- A project idea is still vague and you want a brief, PRD and architecture built step by step with BMAD
- The backlog is ready for development and has to be split into waves of stories that agents can take in parallel
- Before implementation starts you want a readiness check to find gaps in the plans
- Requirements changed mid-sprint and the plan has to be adjusted with the `bmad-correct-course` skill
- An outside development tool should pick up the tasks and needs a `handoff-manifest.json`
Not a fit when
- You need an agent that writes, tests and reviews code itself: the author removed those parts and kept planning only
- The project is small and one task in a plain chat is enough: the BMAD phases add extra steps
- You expect the plugin to launch agents and create worktrees: it only plans parallelism
- You want the full methodology with implementation: BMad Method itself covers that, while this is an independent harness
Example request
Split the ready backlog of stories into parallel waves and write a branch merge planLimitations
This is an independent harness around the BMAD method, not an official product of the BMAD Code Organization: the name and methodology belong to that organization, and the MIT license covers only the plugin code. The plugin runs in Claude Code and installs through the marketplace. The `bmad-parallel-plan` skill only plans waves; it does not launch agents, create worktrees or run git operations. The old script installer was replaced by the plugin, and `MIGRATION.md` covers the switch.
How to disable. Run `/plugin uninstall bmad-planning-orchestrator@bmad-method-harness`, then `/reload-plugins`. Plans and story files already created stay in your project.
FAQ
How do the Quick Flow, BMad Method and Enterprise tracks differ?
The track sets the planning scope and is picked interactively at the start; the `select-track.sh` script helps choose. Quick Flow, BMad Method and Enterprise fit the depth of planning to the size of the work. Details are in `resources/track-selection-guide.md`.
What is a wave of stories?
A group of stories that share no files and whose dependencies are already satisfied, so different agents can build them at the same time. The `maxParallel` parameter caps the wave size, and the plugin records the merge order in `parallelization-plan.md`.
How do I check a plan is ready before development?
Run the `bmad-readiness-check` skill; the readiness-auditor subagent handles it too. For file-overlap checks there is the `scope-conflict-check.sh` script.
Do I need to install BMAD-METHOD itself?
No, the plugin installs on its own and is self-contained: there is no installer, no `npx` and no copying into `~/.claude`. The methodology and links to the original are collected in `ATTRIBUTION.md`.
How do I try the plugin locally without the marketplace?
Run `claude --plugin-dir ./bmad-planning-orchestrator` from the root of a cloned repository. This is handy for testing edits before publishing.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin links planning, implementation and task checks, retains progress and controls how independently agents work.
A Claude Code plugin that turns vague requirements into numbered spec files with a dependency manifest through an interview.
A Claude Code plugin that interviews you, designs the architecture and writes a self-contained blueprint to build from
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
MadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend
A Claude Code plugin for large specs: requirements with proof obligations, a walking skeleton and audited sprints
README in short
The description explains that the repository is a marketplace of a single plugin and links to the BMAD Code Organization, crediting the method to it. Two install commands follow, then the feature list, the reasons for moving from a skills installer to a plugin and a directory layout.