Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bmad-code-org avatar

Sample Module Setup

  • 4 installs
  • 186 repo stars
  • Updated June 22, 2026
  • bmad-code-org/bmad-builder

sample-module-setup is a Claude skill that installs and configures the BMad Samples module into a project, writing its config and help-registry files.

About

sample-module-setup installs and configures a BMad module into a project. It reads module metadata, collects user preferences, and writes shared project config, gitignored personal settings, and a help-registry CSV. It detects fresh installs versus legacy migrations, runs bundled Python merge scripts, and cleans up legacy config directories.

  • Installs and configures a BMad module into a project by writing config.yaml, config.user.yaml, and module-help.csv
  • Collects user preferences and separates shared project config from gitignored personal settings
  • Handles fresh installs and legacy per-module migration with an anti-zombie config pattern

Sample Module Setup by the numbers

  • 4 all-time installs (skills.sh)
  • Ranked #580 of 782 Skill Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

sample-module-setup capabilities & compatibility

Capabilities
module setup · config management
Use cases
orchestration
From the docs

What sample-module-setup says it does

Installs and configures a BMad module into a project.
SKILL.md
Collects user preferences and writes them to three files:
SKILL.md
Both config scripts use an anti-zombie pattern — existing entries for this module are removed before writing fresh ones, so stale values never persist.
SKILL.md
npx skills add https://github.com/bmad-code-org/bmad-builder --skill sample-module-setup

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
repo stars186
Last updatedJune 22, 2026
Repositorybmad-code-org/bmad-builder

What it does

Install and configure the BMad Samples module into a project, writing its config files and registering its capabilities.

Who is it for?

Installing and configuring a BMad module and writing its project and user config files

Skip if: Authoring the module's skills or workflows (that is done by the builder skills)

When should I use this skill?

The user asks to install the samples module, configure BMad Samples, or set up BMad Samples

What you get

A configured module with config.yaml, config.user.yaml, and module-help.csv written and legacy files cleaned up.

  • config.yaml
  • config.user.yaml
  • module-help.csv

By the numbers

  • Writes 3 config files (config.yaml, config.user.yaml, module-help.csv)

Files

SKILL.mdMarkdownGitHub ↗

Module Setup

Overview

Installs and configures a BMad module into a project. Module identity (name, code, version) comes from ./assets/module.yaml. Collects user preferences and writes them to three files:

  • `{project-root}/_bmad/config.yaml` — shared project config: core settings at root (e.g. output_folder, document_output_language) plus a section per module with metadata and module-specific values. User-only keys (user_name, communication_language) are never written here.
  • `{project-root}/_bmad/config.user.yaml` — personal settings intended to be gitignored: user_name, communication_language, and any module variable marked user_setting: true in ./assets/module.yaml. These values live exclusively here.
  • `{project-root}/_bmad/module-help.csv` — registers module capabilities for the help system.

Both config scripts use an anti-zombie pattern — existing entries for this module are removed before writing fresh ones, so stale values never persist.

{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root, not the skill root.

On Activation

1. Read ./assets/module.yaml for module metadata and variable definitions (the code field is the module identifier) 2. Check if {project-root}/_bmad/config.yaml exists — if a section matching the module's code is already present, inform the user this is an update 3. Check for per-module configuration at {project-root}/_bmad/sam/config.yaml and {project-root}/_bmad/core/config.yaml. If either file exists:

  • If {project-root}/_bmad/config.yaml does not yet have a section for this module: this is a fresh install. Inform the user that installer config was detected and values will be consolidated into the new format.
  • If {project-root}/_bmad/config.yaml already has a section for this module: this is a legacy migration. Inform the user that legacy per-module config was found alongside existing config, and legacy values will be used as fallback defaults.
  • In both cases, per-module config files and directories will be cleaned up after setup.

If the user provides arguments (e.g. accept all defaults, --headless, or inline values like user name is BMad, I speak Swahili), map any provided values to config keys, use defaults for the rest, and skip interactive prompting. Still display the full confirmation summary at the end.

Collect Configuration

Ask the user for values. Show defaults in brackets. Present all values together so the user can respond once with only the values they want to change (e.g. "change language to Swahili, rest are fine"). Never tell the user to "press enter" or "leave blank" — in a chat interface they must type something to respond.

Default priority (highest wins): existing new config values > legacy config values > ./assets/module.yaml defaults. When legacy configs exist, read them and use matching values as defaults instead of module.yaml defaults. Only keys that match the current schema are carried forward — changed or removed keys are ignored.

Core config (only if no core keys exist yet): user_name (default: BMad), communication_language and document_output_language (default: English — ask as a single language question, both keys get the same answer), output_folder (default: {project-root}/_bmad-output). Of these, user_name and communication_language are written exclusively to config.user.yaml. The rest go to config.yaml at root and are shared across all modules.

Module config: Read each variable in ./assets/module.yaml that has a prompt field. Ask using that prompt with its default value (or legacy value if available).

Write Files

Write a temp JSON file with the collected answers structured as {"core": {...}, "module": {...}} (omit core if it already exists). Then run both scripts — they can run in parallel since they write to different files:

python3 ./scripts/merge-config.py --config-path "{project-root}/_bmad/config.yaml" --user-config-path "{project-root}/_bmad/config.user.yaml" --module-yaml ./assets/module.yaml --answers {temp-file} --legacy-dir "{project-root}/_bmad"
python3 ./scripts/merge-help-csv.py --target "{project-root}/_bmad/module-help.csv" --source ./assets/module-help.csv --legacy-dir "{project-root}/_bmad" --module-code sam

Both scripts output JSON to stdout with results. If either exits non-zero, surface the error and stop. The scripts automatically read legacy config values as fallback defaults, then delete the legacy files after a successful merge. Check legacy_configs_deleted and legacy_csvs_deleted in the output to confirm cleanup.

Run ./scripts/merge-config.py --help or ./scripts/merge-help-csv.py --help for full usage.

Create Output Directories

After writing config, create any output directories that were configured. For filesystem operations only (such as creating directories), resolve the {project-root} token to the actual project root and create each path-type value from config.yaml that does not yet exist — this includes output_folder and any module variable whose value starts with {project-root}/. The paths stored in the config files must continue to use the literal {project-root} token; only the directories on disk should use the resolved paths. Use mkdir -p or equivalent to create the full path.

Cleanup Legacy Directories

After both merge scripts complete successfully, remove the installer's package directories. Skills and agents in these directories are already installed at .claude/skills/ — the _bmad/ directory should only contain config files.

python3 ./scripts/cleanup-legacy.py --bmad-dir "{project-root}/_bmad" --module-code sam --also-remove _config --skills-dir "{project-root}/.claude/skills"

The script verifies that every skill in the legacy directories exists at .claude/skills/ before removing anything. Directories without skills (like _config/) are removed directly. If the script exits non-zero, surface the error and stop. Missing directories (already cleaned by a prior run) are not errors — the script is idempotent.

Check directories_removed and files_removed_count in the JSON output for the confirmation step. Run ./scripts/cleanup-legacy.py --help for full usage.

Confirm

Use the script JSON output to display what was written — config values set (written to config.yaml at root for core, module section for module values), user settings written to config.user.yaml (user_keys in result), help entries added, fresh install vs update. If legacy files were deleted, mention the migration. If legacy directories were removed, report the count and list (e.g. "Cleaned up 106 installer package files from sam/, core/, \_config/ — skills are installed at .claude/skills/"). Then display the module_greeting from ./assets/module.yaml to the user.

Outcome

Once the user's user_name and communication_language are known (from collected input, arguments, or existing config), use them consistently for the remainder of the session: address the user by their configured name and communicate in their configured communication_language.

Related skills

FAQ

Which files does sample-module-setup write?

It writes _bmad/config.yaml (shared project config), _bmad/config.user.yaml (personal, gitignored settings), and _bmad/module-help.csv (capability registry).

Does it handle upgrading an existing install?

Yes. It detects whether a module section already exists and distinguishes a fresh install from a legacy per-module migration, using legacy values as fallback defaults.

Skill Developmentagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.