bmad-help
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.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
03 SKILL.md 正文
BMad Help
Purpose
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.
Desired Outcomes
When this skill completes, the user should:
- Know where they are — which module and phase they're in, what's already been completed
- Know what to do next — the next recommended and/or required step, with clear reasoning
- Know how to invoke it — skill name, menu code, action context, and any args that shortcut the conversation
- Get offered a quick start — when a single skill is the clear next step, offer to run it for the user right now rather than just listing it
- Feel oriented, not overwhelmed — surface only what's relevant to their current position; don't dump the entire catalog
- Get answers to general questions — when the question doesn't map to a specific skill, use the module's registered documentation to give a grounded answer
Data Sources
- Catalog:
{project-root}/_bmad/_config/bmad-help.csv— assembled manifest of all installed module skills - Config: Run
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}and use the merged JSON to resolveoutput-locationvariables and readcore.communication_languageandmodules.bmm.project_knowledge. The resolver merges_bmad/config.toml,_bmad/config.user.toml,_bmad/custom/config.toml, and_bmad/custom/config.user.tomlin that order. - Artifacts: Files matching
outputspatterns at resolvedoutput-locationpaths reveal which steps are possibly completed; their content may also provide grounding context for recommendations - Project knowledge: If
project_knowledgeresolves to an existing path, read it for grounding context. Never fabricate project-specific details. - Module docs: Rows with
_metain theskillcolumn carry a URL or path inoutput-locationpointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.
CSV Interpretation
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 state- Skills group into folders (
plan,ship; some modules use numbered phases) and flow in order; naming varies by module
Sequencing 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 one- Format:
skill-namefor single-action skills,skill-name:actionfor multi-action skills
Required gates:
required=trueitems must complete before the user can meaningfully proceed to later phases- A phase with no required items is entirely optional — recommend it but be clear about what's actually required next
Completion detection:
- Search resolved output paths for
outputspatterns - Fuzzy-match found files to catalog rows
- User may also state completion explicitly, or it may be evident from the current conversation
Descriptions 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.
Response Format
For each recommended item, present:
[menu-code]Display name — e.g., "[PR] PRD"- Skill name in backticks — e.g.,
bmad-prd - For multi-action skills: action invocation context — e.g., "dev lets run a code review!"
- Description if present in CSV; otherwise your existing knowledge of the skill suffices
- Args if available
Ordering: Show optional items first, then the next required item. Make it clear which is which.
Constraints
- Present all output in
{communication_language} - Recommend running each skill in a fresh context window
- Match the user's tone — conversational when they're casual, structured when they want specifics
- If the active module is ambiguous, retrieve all meta rows remote sources to find relevant info also to help answer their question
04 同仓库更多 Skills
tk-studio-track
Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to "Blocked - Awaiting User" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to "Done"); `reply` posts the owner's answer (or "Done.") with the owner's host-only token and moves the issue to "Block Resolved"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says "block this story", "tk track block", "put it in the owner's inbox", "reply to the blocked issue", "validate the resolution", or a supervisor or engagement payload names this skill.
tk-studio-session
Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says "hand off this run", "tk session", "resume the run", or a boundary/budget trigger says the session must split.
tk-studio-research
Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says "run the ecosystem watch", "tk research", or a research job's invoke-skill directive names this skill.
tk-studio-report
One-verb human defect report — "the skill did the wrong thing" — recorded as a report event in the local measurement ledger. Use when the user says "tk report", "report a defect", "that skill misbehaved", or "log a studio issue".
tk-studio-playable-judge
The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says "judge the playable frames".
tk-studio-plan-sync
Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says "sync the plan", "normalize planning artifacts", "tk plan sync", or after stock BMad planning flows produce or change epics/stories.