Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-help
Orchestration spine and "what do I do next?" router for the BMAD Planning & Orchestrator plugin. Detects current planning state by scanning the output folder for which artifacts exist (project-context.md, decision-log.md, product-brief, prd/tech-spec, architecture, ux, epics, stories), infers the current phase and track, then recommends the next BMAD skill to run — skipping optional phases (Analysis is always optional; UX only when there is a UI).
Passed 15 of 18 test cases with the skill, and 6 of 18 without it.
and 11 more in the full report
12 fixed6 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
A lean router. It answers one question: what do I run next? It detects planning state, infers the phase and track, and points to the next skill. It is auto-invoked to orient a session and replaces a heavyweight master/orchestrator agent.
This skill produces NO planning documents. It reads state and recommends. All artifacts are produced by the specialized planning skills it routes to.
Analysis ──► Planning ──► Solutioning ──► Implementation-handoff
(optional) (required) (conditional) (required: ready-for-dev stories)
| Phase | Artifact(s) | Skill |
|---|---|---|
| Analysis (optional) | product-brief, research, brainstorm | bmad-product-brief / bmad-research / bmad-brainstorm |
| Planning (required) | prd.md OR tech-spec.md, epics.md | bmad-prd / bmad-tech-spec / bmad-epics-and-stories |
| Planning — UX (only if UI) | ux-design.md | bmad-ux |
| Solutioning (track-dependent) | architecture.md | bmad-architecture |
| Implementation-handoff (required) | {epic}.{story}.{slug}.story.md (ready-for-dev) | bmad-epics-and-stories → bmad-sprint-planning |
Threaded across every phase: project-context.md (the project "constitution") and decision-log.md (decisions carried between workflows). If these are missing, the first recommendation is always to establish them.
Implementation itself (writing code, running tests) is OUT OF SCOPE. The last artifact this plugin produces is a ready-for-dev story file or handoff manifest, passed to an external dev tool.
test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.