Agent skill · operations · 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). Use when the user asks "what's next", "what do I do next", "where am I", "what's my status", "continue", "resume planning", "which skill should I run", "what BMAD step is next", or types "/bmad-help" / "/status". Auto-invoke at the start of any BMAD planning session to orient. This skill ROUTES only — it never writes planning documents itself.
Why this skill is useful
Adds specific scripts for detecting planning state and recommending next steps that are tailored to the BMAD framework.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Help — Orchestration Spine 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. When to use User asks "what's next", "where am I", "what's my status", "continue", "resume". Start of any BMAD session, to orient before doing planning work. User is unsure which skill to invoke. Phase Map 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. Tracks (scale-adaptive — never numbered levels) A heuristic may suggest a track from story count; the user confirms. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-help