{setup-skill-name}

Installs and configures a BMad module in a project with YAML/JSON merging and cleanup.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill standardizes the setup of a BMad module inside a project, so users do not have to manually create config files, register help entries, migrate legacy settings, or clean up outdated installer directories.

Core Features & Use Cases

  • Guided module installation: Reads module metadata from the bundled assets and collects both shared core settings and module-specific values.
  • Safe config migration: Consolidates legacy per-module configuration into shared project config files while preserving valid existing values and removing stale entries.
  • Automated cleanup and registration: Updates the module help CSV, creates configured output directories, and removes old installer package directories only after verifying installed skills are present.
  • Use case: When a team wants to add or update a BMad module in an existing repository, this Skill can install it, merge old settings into the new config structure, and leave the project in a clean, consistent state.

Quick Start

Ask the assistant to set up the target BMad module in your project and provide any preferred defaults such as your name, language, or headless installation choices.

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 YAML config files into a shared project structure?

To migrate legacy YAML config files, this Skill consolidates per-module configuration into shared project config files, preserving valid existing values while removing stale entries. It uses YAML and JSON driven config merging to ensure old settings integrate cleanly into the current structure.

How do I safely clean up old installer directories after a module migration?

Safely cleaning up old installer directories requires verified removal, which this Skill performs by checking that installed skills are present before deleting legacy module directories. This anti-zombie replacement ensures stale module sections are removed only after successful migration.

Can I automate BMad module setup and help CSV registration in an existing repository?

Yes, you can automate BMad module setup in an existing repository. This Skill reads module metadata, collects shared core and module-specific settings, creates configured output directories, and automatically updates the module help CSV during installation.

Does this module configuration tool require pyyaml for YAML merging?

Yes, this module configuration tool requires the pyyaml dependency to parse and merge YAML driven configuration files. It relies on this library to consolidate legacy per-module config files into the current shared project structure.

What is anti-zombie replacement when updating module configuration files?

Anti-zombie replacement is the process of overwriting stale module sections in configuration files during an update. This Skill applies this mechanism to ensure that outdated or orphaned config entries are replaced rather than lingering alongside new settings.

What is the best way to handle fresh installs versus legacy migrations for project modules?

The best way to handle both fresh installs and legacy migrations is using an automated setup Skill that standardizes directory creation, config merging, and cleanup. It collects settings, writes shared and user config files, and registers help entries for both scenarios.