{setup-skill-name}

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

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Hexalith/Hexalith.Parties --skill setup-skill-name-hexalith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: {setup-skill-name}
Source: https://github.com/Hexalith/Hexalith.Parties/tree/main/.agents/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/Hexalith/Hexalith.Parties --skill setup-skill-name-hexalith

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 shared project config, personal user settings, and help-system registrations across multiple files, while also migrating legacy per-module config without leaving stale values behind. This Skill automates that entire installation and migration workflow. ## Core Features & Use Cases - Config Merging: Writes core settings at the root of _bmad/config.yaml and module-specific values under a module section, using an anti-zombie pattern that removes stale entries before writing fresh ones. - User Settings Separation: Stores user_name, communication_language, and any variable marked user_setting: true exclusively in the gitignored config.user.yaml. - Legacy Migration: Reads old per-module config files as fallback defaults, deletes legacy config and CSV files, and removes installer package directories after verifying skills are installed at .claude/skills/. - Use Case: A user asks to install the 'bmb' module; the Skill collects preferences, merges them into shared config, registers help entries, cleans up legacy directories, and confirms the result with the module greeting. ## Quick Start Ask the assistant to install and configure the BMad module for your project, optionally providing values like your name and preferred language inline.

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?

Invoke the setup skill and provide values inline or answer the prompts. It reads module.yaml for defaults, writes config.yaml and config.user.yaml under _bmad/, registers help entries, and cleans up legacy installer directories.

How does BMad module config migration from legacy files work?

The merge scripts read legacy per-module config.yaml files as fallback defaults, with explicit answers taking priority. After a successful merge, the legacy config files and module-help.csv files are deleted automatically.

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 is gitignored and stores personal settings such as user_name, communication_language, and variables marked user_setting: true.

Why does the setup script reject the {project-root} token?

The {project-root} token is only valid inside config values, not filesystem path arguments. Scripts exit with an error if it appears in path arguments, so you must resolve it to the actual project root before running.

Is it safe to re-run the BMad module setup skill?

Yes. The anti-zombie pattern removes existing module entries before writing fresh ones, and the cleanup script is idempotent, treating already-removed directories as non-errors.