agentleFS
Brumm-LabsBrumm-Labs/kb-agents/.claude/skills/bmad-help/SKILL.md

bmad-help

Skill1 starsChanged 7 months agoMITView on GitHub

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.

25 other projects use a version of this, 21 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use bmad-dev-auto, bmad-checkpoint-preview and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • areesh-aliSkill

    bmad-dev-auto

    One iteration of an unattended development loop. Use when invoked by name.

    Also in 8 projects that use this

  • GauravRatnawatSkill

    bmad-checkpoint-preview

    LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".

    Also in 15 projects that use this

  • 2233adminSkill

    bmad-editorial-review

    Deprecated — forwards to bmad-review.

    Also in 6 projects that use this

  • 2233adminSkill

    bmad-review-verification-gap

    Deprecated — forwards to bmad-review.

    Also in 6 projects that use this

  • DogaOztuzunSkill

    bmad-agent-tech-writer

    Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

    Also in 13 projects that use this

  • GauravRatnawatSkill

    bmad-prfaq

    Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.

    Also in 16 projects that use this

  • +1 more from GauravRatnawat

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 1 is distinctive, and 2 are very specific to this project.

  • 1

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    When this skill completes, the user should:

    line 14
  2. Very specific:

    Project knowledge: If project_knowledge resolves to an existing path, read it for grounding context.

    line 27
  3. Very specific:

    Search resolved output paths for outputs patterns

    line 51
  4. Distinctive:

    If the active module is ambiguous, ask rather than guess

    line 73

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BMad Help

Purpose

Help the user understand where they are in their BMad workflow and what to do next. Answer BMad questions when asked.

Desired Outcomes

When this skill completes, the user should:

  1. Know where they are — which module and phase they're in, what's already been completed
  2. Know what to do next — the next recommended and/or required step, with clear reasoning
  3. Know how to invoke it — skill name, menu code, action context, and any args that shortcut the conversation
  4. 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
  5. Feel oriented, not overwhelmed — surface only what's relevant to their current position; don't dump the entire catalog

Data Sources

  • Catalog: {project-root}/_bmad/_config/bmad-help.csv — assembled manifest of all installed module skills
  • Config: config.yaml and user-config.yaml files in {project-root}/_bmad/ and its subfolders — resolve output-location variables, provide communication_language and project_knowledge
  • Artifacts: Files matching outputs patterns at resolved output-location paths reveal which steps are possibly completed; their content may also provide grounding context for recommendations
  • Project knowledge: If project_knowledge resolves to an existing path, read it for grounding context. Never fabricate project-specific details.

CSV Interpretation

The catalog uses this format:

module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs

Phases determine the high-level flow:

  • anytime — available regardless of workflow state
  • Numbered phases (1-analysis, 2-planning, etc.) flow in order; naming varies by module

Dependencies determine ordering within and across phases:

  • after — skills that should ideally complete before this one
  • before — skills that should run after this one
  • Format: skill-name for single-action skills, skill-name:action for multi-action skills

Required gates:

  • required=true items 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 outputs patterns
  • 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., "[CP] Create PRD"
  • Skill name in backticks — e.g., bmad-create-prd
  • For multi-action skills: action invocation context — e.g., "tech-writer lets create a mermaid diagram!"
  • 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, ask rather than guess

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.