{setup-skill-name}

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill setup-skill-name-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: {setup-skill-name}
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-module-builder/assets/setup-skill-template
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill setup-skill-name-hordricjr

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 in a project requires writing configuration to multiple files, migrating legacy per-module configs, and registering help entries — doing this by hand is error-prone and leaves stale values behind. ## Core Features & Use Cases - Config Merging: Collects user preferences and writes them to _bmad/config.yaml (shared settings) and _bmad/config.user.yaml (personal settings like user_name and communication_language) using an anti-zombie pattern that removes stale entries before writing. - 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 capabilities into module-help.csv and removes legacy installer directories after verifying skills are installed at .claude/skills/. - Use Case: A user says "install the bmb module" — the skill reads module.yaml, prompts for preferences, writes both config files, registers help entries, and cleans up legacy directories in one guided flow. ## Quick Start Ask the assistant to install and configure the module in this project, optionally providing values inline such as your name and preferred language to skip interactive prompts.

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 for the module, which reads module.yaml, prompts for configuration values, and writes them to _bmad/config.yaml and config.user.yaml. You can pass values inline, such as your name and language, to skip interactive prompting.

How does BMad module config migration from legacy files work?

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

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

config.yaml holds shared project settings like output_folder and module metadata, while config.user.yaml stores personal settings like user_name and communication_language and is intended to be gitignored. User-only keys are never written to the shared config.

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

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

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

Yes. The scripts use an anti-zombie pattern that removes existing module entries before writing fresh ones, and the cleanup script is idempotent — already-removed directories are reported as not found rather than causing errors.