{setup-skill-name}

Install and update BMad modules by merging YAML metadata and config into shared project files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the friction of installing and updating a BMad module by gathering the right configuration, merging it into the shared project setup, and cleaning up obsolete legacy files safely.

Core Features & Use Cases

  • Module discovery and setup: Reads module metadata and prompts for core and module-specific values needed for installation.
  • Config migration: Consolidates shared settings into centralized config files while preserving valid legacy values as fallback defaults.
  • Help-system registration: Merges module help entries into the shared help catalog and removes stale duplicates.
  • Legacy cleanup: Deletes outdated installer directories only after verifying the skill is installed in the target skills directory.

Quick Start

Ask the skill to install or update a BMad module in your project and provide any preferences you want applied during the configuration step.

Frequently Asked Questions about {setup-skill-name}

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

FAQPage Schema
How do I merge module configuration values into a shared project setup?

You can merge module configuration values into a shared project setup by reading module YAML definitions and applying anti-zombie merges to consolidate settings into centralized config files while preserving valid legacy values as fallback defaults.

What is the best way to clean up legacy installer directories during module migration?

The best way to clean up legacy installer directories during module migration is to verify the skill is installed in the target skills directory first, then safely remove the obsolete legacy files to prevent broken dependencies.

How does help registration work when onboarding a new module?

Help registration works when onboarding a new module by merging module help entries into the shared help catalog and removing stale duplicates to maintain a single source of truth for project documentation.

Do I need pyyaml to install BMad modules in my project?

Yes, you need pyyaml installed because the setup process requires reading module YAML definitions to extract metadata and configuration values necessary for the installation flow.

Can I update an existing module configuration without losing previous settings?

You can update an existing module configuration without losing previous settings because the merge process preserves valid legacy values as fallback defaults while applying new metadata and configuration entries.

Why does my module setup fail when legacy directories are removed too early?

Module setup fails when legacy directories are removed too early because the system deletes outdated installer directories only after verifying the skill is installed in the target skills directory to ensure reproducible setup.