skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

{setup-skill-name}

Set up and migrate a BMad module by merging metadata and preferences into shared config files.

1|Updated Mar 31, 2026
Search Tags:#yaml#csv#bmad#module setup#config migration#legacy cleanup
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill setup-skill-name-mol4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: {setup-skill-name}
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/mol4/BMAD-Board --skill setup-skill-name-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the manual work of installing and updating a BMad module by consolidating module metadata, user preferences, and legacy configuration into the current project structure.

Core Features & Use Cases

  • Installs module settings into shared project config files while keeping user-only values separate.
  • Detects fresh installs, updates, and legacy migrations, then applies sensible defaults and anti-zombie merging.
  • Registers help entries, creates output directories, and cleans up obsolete installer directories after a successful setup.

Quick Start

Use this skill to set up a BMad module in a project by supplying the module metadata and preferences you want preserved.

Frequently Asked Questions about {setup-skill-name}

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

FAQPage Schema
How do I merge BMad module metadata into existing project configuration files?▼

Merge BMad module metadata into shared project YAML configuration files by validating module.yaml definitions and applying user preferences while keeping user-only values separate from shared settings.

What is the best way to migrate legacy config files during a module setup?▼

Migrate legacy config files during module setup by applying anti-zombie config merging and legacy fallback defaults to safely consolidate old settings into the current project structure.

Does module setup require pyyaml to validate module.yaml definitions?▼

Yes, module setup requires the pyyaml dependency to parse YAML files, validate module.yaml definitions, and merge configuration metadata into the shared project config files.

Can I clean up obsolete installer directories automatically after a module installation?▼

Clean up obsolete installer package directories automatically after a successful module installation completes, which also registers help entries and creates output directories from the project-root token.

How does the config migration handle fresh installs versus updates?▼

Config migration detects fresh installs, updates, and legacy migrations, then applies sensible defaults and anti-zombie merging to safely consolidate module metadata into shared configuration files.

What limitations should I expect when consolidating legacy config fallbacks?▼

Consolidating legacy config fallbacks requires valid module.yaml definitions and proper project-root tokens to create output directories, meaning invalid YAML metadata will block the setup and migration process.

Related Skills

Explore More Software Engineering Skills→
Rinzler78Rinzler78
1

bmad-bmb-setup

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

Community
Advanced
amitmishra-bylddamitmishra-byldd

bmad-bmb-setup

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

Community
Advanced
amitmishra-bylddamitmishra-byldd

{ setup-skill-name }

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

Community
Advanced
devalexanderdazadevalexanderdaza

{setup-skill-name}

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

Community
Advanced