skills.rest
amitmishra-byldd
amitmishra-bylddCOMMUNITY
Explore all skills by this author →
GitHub

bmad-bmb-setup

Consolidate BMad Builder module configs and help entries into project-level YAML files.

Updated Apr 2, 2026
Search Tags:#automation#migration#configuration#merge#csv#bmad#module-install
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-bmb-setup-amitmishra-byldd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-bmb-setup
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmb/bmad-bmb-setup
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-bmb-setup-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

Consolidates installation and configuration of the BMad Builder module into a single, consistent project-level setup. It prevents stale or duplicate per-module config by removing legacy entries, consolidating core and module settings, and ensuring user-only settings remain private. The Skill coordinates writing shared config, user config, and help registry entries while verifying success and cleanup.

Core Features & Use Cases

  • Consolidated Config Writes: Writes _bmad/config.yaml for shared settings, _bmad/config.user.yaml for personal keys, and updates _bmad/module-help.csv for help entries.
  • Legacy Migration & Anti-Zombie Pattern: Detects legacy per-module configs, uses legacy values as fallback defaults, removes old module sections before writing fresh ones, and deletes legacy files on success.
  • Scripted Validation & Cleanup: Runs merge-config.py, merge-help-csv.py, and cleanup-legacy.py with JSON output checks and safety verification for installed skills; creates configured output directories on disk while preserving {project-root} tokens in config.
  • Use Case: Migrate a project that previously stored per-module configs into the centralized _bmad layout, preserving user preferences and cleaning up installer artifacts.

Quick Start

Set up the BMad Builder module in this project and migrate any legacy per-module configs into the shared _bmad configuration.

Frequently Asked Questions about bmad-bmb-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy per-module configs into a centralized project-level config.yaml?▼

Migrating legacy per-module configs into a centralized config.yaml involves detecting old module sections, using their values as fallback defaults, and removing stale entries before writing fresh consolidated settings. The process writes shared config.yaml and private config.user.yaml while deleting legacy files on success.

What's the best way to consolidate CSV help entries during a module configuration migration?▼

Consolidating CSV help entries during module configuration migration runs a merge-help-csv.py script that combines per-module help rows into a centralized module-help.csv file. The process validates JSON output from the merge script and verifies safety before completing the migration.

Why do I get duplicate or stale module sections after updating my project configuration?▼

Duplicate or stale module sections appear when legacy per-module configs are not removed before writing fresh settings. An anti-zombie replacement pattern detects old module sections, removes them, and writes clean consolidated entries to prevent conflicts during installation or migration.

Does the BMad Builder setup preserve user-only settings when merging shared configuration files?▼

The BMad Builder setup preserves user-only settings by writing personal keys to a separate config.user.yaml file while shared settings go to config.yaml. This separation ensures private preferences remain intact during module installation and legacy migration.

Can I use YAML configuration merging to clean up installer artifacts and legacy files?▼

YAML configuration merging cleans up installer artifacts by running a cleanup-legacy.py script after validating merge outputs. The script deletes legacy per-module config files only after JSON output checks confirm successful consolidation of core and module settings.

When do I need to run merge and cleanup scripts for module configuration consolidation?▼

Merge and cleanup scripts for module configuration consolidation are needed during fresh BMad Builder module installs or legacy migrations from per-module configs. The scripts handle writing config.yaml, config.user.yaml, and module-help.csv while creating configured output directories and validating results.

Related Skills

Explore More Software Engineering Skills→
ncptuanncptuan

{setup-skill-name}

Installs and configures a BMad module in a project with YAML/JSON merging and cleanup.

Community
Advanced
b566776b566776

bmad-bmb-setup

Install and configure the BMad Builder module by generating config files.

Community
Advanced
diegosanchespereira1diegosanchespereira1

bmad-module-builder

Plan, scaffold, and validate BMad module structures from skill directories.

Community
Advanced
Rinzler78Rinzler78
1

bmad-bmb-setup

Install and configure the BMad Builder module by merging YAML settings into shared config files.

Community
Advanced