name: help
phase = anytime — Universal tools work regardless of workflow state1-discover → 2-define → 3-build → 4-ship flow in order (naming varies by module)required=true blocks progress — Required workflows must complete before proceeding to later phasesoutputs patterns, fuzzy-match found files to workflow rowsWhen command field has a value:
/ (e.g., /bmad-bmm-create-prd)When command field is empty:
/agent-commandcode field or describing the name fieldExample presentation for empty command:
Explain Concept (EC)
Load: /tech-writer, then ask to "EC about [topic]"
Agent: Tech Writer
Description: Create clear technical explanations with examples...
module column → universal tools (work across all modules)module → module-specific workflowsDetect the active module from conversation context, recent workflows, or user query keywords. If ambiguous, ask the user.
Determine what was just completed:
outputs patternsindex.md exists, read it for additional contextLoad catalog — Load {project-root}/_bmad/_config/bmad-help.csv
Resolve output locations and config — Scan each folder under {project-root}/_bmad/ (except _config) for config.yaml. For each workflow row, resolve its output-location variables against that module's config so artifact paths can be searched. Also extract communication_language and project_knowledge from each scanned module's config.
Ground in project knowledge — If project_knowledge resolves to an existing path, read available documentation files (architecture docs, project overview, tech stack references) for grounding context. Use discovered project facts when composing any project-specific output. Never fabricate project-specific details — if documentation is unavailable, state so.
Detect active module — Use MODULE DETECTION above
Analyze input — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
Present recommendations — Show next steps based on:
Optional items first — List optional workflows until a required step is reached Required items next — List the next required workflow
For each item, apply DISPLAY RULES above and include:
Additional guidance to convey:
{communication_language}Return to the calling process after presenting recommendations.