com um clique
bmad-module-builder
// 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'.
// 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'.
Dream journal, interpretation, and lucid dreaming coach. Use when the user wants to talk to Oneira, requests the Dream Guide, or wants help with dream journaling, interpretation, or lucid dreaming.
Sets up BMad Samples module in a project. Use when the user requests to 'install samples module', 'configure BMad Samples', or 'setup BMad Samples'.
Sets up BMad Builder module in a project. Use when the user requests to 'install bmb module', 'configure BMad Builder', or 'setup BMad Builder'.
Sets up {module-name} module in a project. Use when the user requests to 'install {module-code} module', 'configure {module-name}', or 'setup {module-name}'.
Builds, edits, and analyzes workflows and skills. Use when the user requests to "build a workflow", "modify a workflow", "quality check workflow", or "analyze skill".
Run a skill's evals in a clean, isolated environment and report results. Use when the user wants to evaluate a skill, run evals, benchmark a skill, validate triggers, or grade skill outputs.
| name | bmad-module-builder |
| description | 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'. |
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:
-setup skill. For single skills, embeds self-registration directly into the skill. Supports --headless / -H.--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.
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:
./references/ideate-module.md./references/create-module.md./references/validate-module.mdIf --headless or -H is passed, route to CM with headless mode.