{setup-skill-name}

Installs and configures BMad modules by merging YAML configs and help CSV entries.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill setup-skill-name-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: {setup-skill-name}
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill setup-skill-name-jgabriellima

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 writing configuration values to multiple files, migrating legacy per-module configs, registering help entries, and cleaning up installer directories. Doing this manually is error-prone and leaves stale config values behind. ## Core Features & Use Cases - Config Merging: Writes core settings and module-specific values into shared config.yaml and config.user.yaml files using an anti-zombie pattern that removes stale entries before writing fresh ones. - 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 at .claude/skills/. - Use Case: When a user asks to install or configure a BMad module, this skill collects preferences, writes the three config files, creates output directories, and cleans up legacy installer packages in one guided flow. ## Quick Start Ask the agent to install and configure the BMad module for your project, providing any preferences such as your name and preferred language. ## Quick Start Install the BMad module in my project and configure it with my user name and preferred language.

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 and configure a BMad module in my project?▼

Invoke the setup skill, which reads module.yaml for variable definitions, prompts for configuration values with defaults, then runs merge scripts to write config.yaml, config.user.yaml, and module-help.csv under the _bmad directory.

How does BMad module setup handle legacy config migration?▼

The merge scripts read old per-module config files from _bmad/{module-code}/ and _bmad/core/, use matching values as fallback defaults, and delete the legacy files after a successful merge. Legacy directories are removed only after verifying skills exist at .claude/skills/.

What is the difference between config.yaml and config.user.yaml in BMad?▼

config.yaml holds shared project settings like output_folder and module values, while config.user.yaml stores personal gitignored settings such as user_name, communication_language, and any module variable marked user_setting: true.

Can I run BMad module setup non-interactively with default values?▼

Yes, pass arguments such as accept all defaults, --headless, or inline values like a user name and language. Provided values map to config keys, defaults fill the rest, and a full confirmation summary is still displayed.

What happens if the BMad cleanup script finds missing skills?▼

The cleanup-legacy.py script verifies every skill in legacy directories exists at .claude/skills/ before removing anything. If any skill is missing, it exits with an error listing the missing skills and removes nothing.