{setup-skill-name}

Installs and configures BMad modules by merging settings into shared YAML config files.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill setup-skill-name-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: {setup-skill-name}
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/Wizarck/nexandro --skill setup-skill-name-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Setting up a BMad module requires collecting user preferences, merging them into shared configuration files, migrating legacy per-module configs, and cleaning up installer directories — a multi-step process that is error-prone when done manually. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into _bmad/config.yaml and personal settings into _bmad/config.user.yaml using an anti-zombie pattern that removes stale entries. - Legacy Migration: Detects old per-module config files, uses their values as fallback defaults, and deletes them after a successful merge. - Help Registration & Cleanup: Merges module help entries into module-help.csv and removes legacy installer directories after verifying skills are installed. - Use Case: When a user asks to install or configure a BMad module, this Skill collects preferences, writes the config files, registers help entries, and cleans up legacy directories in one guided flow. ## Quick Start Ask the assistant to install and configure the BMad module for this project using the setup skill.

Frequently Asked Questions about {setup-skill-name}

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

FAQPage Schema
How do I install a BMad module in my project?▼

Activate the module setup skill, which reads module.yaml for variable definitions, prompts for configuration values with defaults, and writes them to _bmad/config.yaml and config.user.yaml. It also registers help entries and cleans up legacy installer directories.

How does BMad module config migration from legacy files work?▼

The merge-config.py script reads legacy per-module config.yaml files from _bmad/{module-code}/ and _bmad/core/, uses matching values as fallback defaults, and deletes the legacy files after a successful merge. Explicit answers always override legacy values.

What is the anti-zombie pattern in BMad config merging?▼

The anti-zombie pattern removes all existing entries for a module from config.yaml and module-help.csv before writing fresh ones. This guarantees stale values from previous installations never persist alongside new configuration.

Where are BMad user settings like user_name stored?▼

User-only keys such as user_name and communication_language are written exclusively to _bmad/config.user.yaml, which is intended to be gitignored. They are stripped from the shared config.yaml so personal settings never leak into version control.

What Python dependencies does the BMad module setup require?▼

The setup scripts require Python 3.9 or higher. Only merge-config.py needs an external package, pyyaml, declared as a PEP 723 inline dependency; the other scripts use only the standard library.