メニュー
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/opencardev/crankshaft --skill bmad-helpコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | bmad-help |
| description | Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad. |
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 skillsuv run --python 3.11 {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} and use the merged JSON to resolve output-location variables and read core.communication_language and modules.bmm.project_knowledge. The resolver merges _bmad/config.toml, , , and in that order._bmad/config.user.toml_bmad/custom/config.toml_bmad/custom/config.user.tomloutputs 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}