agentleFS
Sign inStart free
GauravRatnawatGauravRatnawat/claude-cost-optimizer/.claude/skills/bmad-module-builder/SKILL.md

bmad-module-builder

Skill0 starsChanged 7 months agoMITView on GitHub

Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If --headless or -H is passed, route to CM with headless mode.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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 Module Builder

Overview

This skill helps you bring BMad modules to life — from the first spark of an idea to a fully scaffolded, installable module. It offers three paths:

  • Ideate Module (IM) — A creative brainstorming session that helps you imagine what your module could be, decide on the right architecture (agent vs. workflow vs. both), and produce a detailed plan document. The plan then guides you through building each piece with the Agent Builder and Workflow Builder.
  • Create Module (CM) — Takes an existing folder of built skills (or a single skill) and scaffolds the module infrastructure that makes it installable. For multi-skill modules, generates a dedicated -setup skill. For single skills, embeds self-registration directly into the skill. Supports --headless / -H.
  • Validate Module (VM) — Checks that a module's structure is complete and correct — every skill has its capabilities registered, entries are accurate and well-crafted, and structural integrity is sound. Handles both multi-skill and standalone modules. Supports --headless / -H.

Args: Accepts --headless / -H for CM and VM paths, an initial description for IM, or a path to a skills folder or single SKILL.md file for CM/VM.

On Activation

Load available config from {project-root}/_bmad/config.yaml and {project-root}/_bmad/config.user.yaml (root level and bmb section). If neither exists, fall back to {project-root}/_bmad/bmb/config.yaml (legacy per-module format). If still missing, let the user know bmad-builder-setup can configure the module at any time. Use sensible defaults for anything not configured.

Detect user's intent:

  • Ideate / Plan keywords or no path argument → Load ./references/ideate-module.md
  • Create / Scaffold keywords, a folder path, or a path to a single SKILL.md file → Load ./references/create-module.md
  • Validate / Check keywords → Load ./references/validate-module.md
  • Unclear → Present options:
    • Ideate Module (IM) — "I have an idea for a module and want to brainstorm and plan it"
    • Create Module (CM) — "I've already built my skills and want to package them as a module"
    • Validate Module (VM) — "I want to check that my module's setup skill is complete and correct"

If --headless or -H is passed, route to CM with headless mode.

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.

Check your setup, free