{ setup-skill-name }

Install and consolidate BMad module configuration into shared _bmad files.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ImaginerLabs/skill-manager --skill setup-skill-name
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: { setup-skill-name }
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/.trae/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill setup-skill-name

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Installs and consolidates BMad module configuration into a project's shared _bmad configuration, avoiding fragmented per-module settings and preventing stale or duplicate values during installs and migrations.

Core Features & Use Cases

  • Module discovery: Reads module metadata and variable definitions from assets/module.yaml to identify module code, defaults, and prompts.
  • Config consolidation: Collects core and module values, applies legacy defaults when present, and writes shared _bmad/config.yaml and per-user _bmad/config.user.yaml using an anti-zombie pattern to remove stale module sections before writing.
  • Help registration & cleanup: Merges module help entries into _bmad/module-help.csv, runs cleanup of legacy per-module config and directories, and creates configured output directories while preserving literal {project-root} tokens in stored values.
  • Headless and interactive modes: Supports argument-driven headless installs (accept-all-defaults, inline values) and interactive prompting with clear defaults and migration notices.

Quick Start

Run the module setup to install or migrate the module, applying defaults and preserving user-only settings.

Frequently Asked Questions about { setup-skill-name }

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

FAQPage Schema
How do I migrate legacy per-module configuration files into a shared setup?

To migrate legacy per-module configuration, run the setup script to consolidate fragmented settings into a shared _bmad/config.yaml. It applies an anti-zombie pattern to remove stale duplicate sections and merges legacy defaults automatically during the deployment workflow.

How do I install BMad modules without duplicate or stale configuration values?

Install BMad modules by running the setup script which reads assets/module.yaml and writes shared configuration files. It uses an anti-zombie removal pattern to clean stale module sections before writing, preventing duplicate values across fresh installs and updates.

Can I run module configuration and migration in a headless CI/CD pipeline?

Yes, you can run module configuration in headless mode using argument-driven installs with accept-all-defaults and inline values. This allows automated deployment workflows to merge shared configs and CSV help files without interactive prompting.

What is the best way to consolidate fragmented BMad module settings into a shared config?

The best way to consolidate fragmented BMad settings is using a setup script that merges core and module values into shared config.yaml files. It preserves literal project-root tokens and user-only settings while cleaning up legacy directories.

Do I need pyyaml to manage BMad module configuration and help file registration?

Yes, you need the pyyaml dependency to manage BMad configuration because the provided Python scripts parse and merge YAML configuration files. The scripts also handle help registration by merging entries into a shared module-help.csv file.