Help us improve
Share bugs, ideas, or general feedback.
From bmad-pro-skills
Orients users within a BMad workflow by identifying current module and phase, recommending next skills with reasoning, and answering module-related questions from documentation.
npx claudepluginhub bmad-code-org/bmad-method --plugin bmad-pro-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/bmad-pro-skills:bmad-helpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Guides building and testing MVPs using BMAD Method with PMF context files (icp.md, value-prop.md, mvp.md). Activates on 'build it', 'BMAD', 'implement', or 'build & test' validation.
Routes natural language requests to skills and workflows by parsing intent and matching patterns for SDLC phases, gate checks, artifacts, security reviews, and marketing tasks.
Share bugs, ideas, or general feedback.
Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
When this skill completes, the user should:
{project-root}/_bmad/_config/bmad-help.csv — assembled manifest of all installed module skillsconfig.yaml and user-config.yaml files in {project-root}/_bmad/ and its subfolders — resolve output-location variables, provide communication_language and project_knowledgeoutputs patterns at resolved output-location paths reveal which steps are possibly completed; their content may also provide grounding context for recommendationsproject_knowledge resolves to an existing path, read it for grounding context. Never fabricate project-specific details._meta in the skill column carry a URL or path in output-location pointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.The catalog uses this format:
module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
Phases determine the high-level flow:
anytime — available regardless of workflow state1-analysis, 2-planning, etc.) flow in order; naming varies by moduleSequencing determines recommended ordering within and across phases (these are soft suggestions, not hard gates — see required for gating):
preceded-by — skills that should ideally complete before this onefollowed-by — skills that should ideally run after this oneskill-name for single-action skills, skill-name:action for multi-action skillsRequired gates:
required=true items must complete before the user can meaningfully proceed to later phasesCompletion detection:
outputs patternsDescriptions carry routing context — some contain cycle info and alternate paths (e.g., "back to DS if fixes needed"). Read them as navigation hints, not just display text.
For each recommended item, present:
[menu-code] Display name — e.g., "[PR] PRD"bmad-prdOrdering: Show optional items first, then the next required item. Make it clear which is which.
{communication_language}