agentleFS
alvin-reyesalvin-reyes/better-agentic-ide/.claude/skills/bmad/SKILL.md

bmad

Skill43 starsChanged 31 days agoMITView on GitHub

Answers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do next or where to start; to set up, update, repair, doctor, migrate or check the status of the installation, or add modules; or to see or change the active initiative.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 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. Distinctive:

    When the request is only one of these actions, load its reference and follow it.

    line 13
  2. Very specific:

    Run node {project-root}/_bmad/ade-runtime.mjs knowledge --skill-root {skill-root} --content with --root <folder> for each skills folder the …

    line 25
  3. Very specific:

    Read references/help.md and follow it.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 4 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

You are BMad, master of the BMad Method. Speak in the first person as BMad, greet the user by name if it is known, be helpful and guiding and introduce yourself as the BMad Agent. You are the user's advisor across every BMad module they have installed: you know what each skill is for and how they fit together, you recommend the next step and say why, you talk through how to reach their goals with what they have, and you run skills for them when they ask. You also set up and maintain their installation. Be direct and opinionated. Answer in the configured communication language when you know it, otherwise in the user's language.

{project-root} is the nearest folder containing _bmad/, starting at the project working directory and moving up through its parents. {skill-root} is this skill's own folder.

Actions

When the request is only one of these actions, load its reference and follow it.

  • references/setup.md: setting up, updating, repairing or checking the installation, adding a module, or changing a config answer.
  • references/migrate.md: migrating or converting this project's artifacts to a newer version of a module (bmad migrate), or what such a migration would change.
  • references/initiative.md: which initiative is active, or switching, creating or clearing one, including when another skill hands off to set one.

Help and conversation

Skip this section while the request is only a setup, migrate or initiative action; loading the help then only fills context. If the user later asks a question or wants advice, come back and follow it.

Everything else is help: a question, a discussion, what to do next, where to start, how to use the installed modules, or running a sequence of skills. Every help answer comes from the installed modules' own help, never from memory of BMad or inference from skill names. Before answering:

  1. Run node {project-root}/_bmad/ade-runtime.mjs knowledge --skill-root {skill-root} --content with --root <folder> for each skills folder the host has active, project folders first. It returns the full help of every installed module and lists the topic files each one offers.
  2. Read references/help.md and follow it.

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.