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

{ setup-skill-name }

Install and consolidate BMad module configuration into shared _bmad config files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Installs and consolidates a BMad module's configuration into a project's shared _bmad configuration, preventing stale or duplicate settings and migrating legacy per-module configs into a single unified format while keeping user-only settings separate.

Core Features & Use Cases

  • Automated installation and consolidation: Reads module metadata and prompts (assets/module.yaml), collects answers, and writes consolidated _bmad/config.yaml and _bmad/config.user.yaml using an anti-zombie pattern so old entries are removed before writing.
  • Legacy migration and cleanup: Detects legacy per-module config and core config, uses matching legacy values as fallback defaults, runs deterministic merge scripts, confirms JSON results, and removes legacy files and directories once migration is successful.
  • Filesystem and help registration: Merges module-help.csv entries into the shared help CSV, creates configured output directories (resolving {project-root} for filesystem operations only), and reports exact changes for user confirmation.
  • Use Case: When integrating a new BMad module into an existing project, use this Skill to migrate any legacy installer config, consolidate settings, register help entries, and remove redundant installer directories safely.

Quick Start

Ask the assistant to install {module-code} into the project and provide or accept configuration values so it can merge configs, register help entries, and clean up legacy installer files.

Frequently Asked Questions about { setup-skill-name }

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

FAQPage Schema
How do I consolidate BMad module configuration into a shared project config?▼

Consolidate BMad module configuration by reading metadata from module.yaml, applying anti-zombie merging, and writing unified settings to shared config.yaml and config.user.yaml files while keeping user-only settings separate.

What is the best way to migrate legacy per-module config files during a BMad installation?▼

Migrate legacy per-module config by detecting existing configuration, using matching legacy values as fallback defaults, running deterministic merge scripts, and removing legacy files and directories only after successful migration.

How does anti-zombie merging work when installing BMad modules?▼

Anti-zombie merging removes old or stale configuration entries before writing new settings, preventing duplicate or outdated values from persisting in the consolidated config.yaml and config.user.yaml files.

Do I need pyyaml to run BMad module installation and migration scripts?▼

Yes, pyyaml is a required dependency for parsing YAML metadata and configuration files during the BMad module installation, consolidation, and legacy migration processes.

Can I register module help entries while consolidating BMad configuration?▼

Yes, the installation process merges module-help.csv entries into the shared help CSV file, creates configured output directories, and reports exact filesystem changes for user confirmation.

Why are my legacy BMad installer directories not being removed after migration?▼

Legacy BMad installer directories are only removed after the migration is confirmed successful, ensuring existing legacy values are safely used as fallback defaults and deterministic merge scripts complete without errors.

Related Skills

Explore More Software Engineering Skills→
devalexanderdazadevalexanderdaza

bmad-bmb-setup

Automate BMad Builder module installation and legacy config migration.

Community
Intermediate
AvatarGanymedeAvatarGanymede

clean-branches

Delete local git branches and worktrees deleted on the remote.

Community
Basic
amitmishra-bylddamitmishra-byldd

bmad-bmb-setup

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

Community
Advanced
devalexanderdazadevalexanderdaza

{setup-skill-name}

Install BMad modules and migrate legacy configs into _bmad/config.yaml.

Community
Advanced