bmad-dev-auto

Redirects deprecated bmad-dev-auto invocations to bmad-build-auto after migrating legacy customization files.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-dev-auto-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-auto
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-dev-auto
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-dev-auto-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents breakage when users still invoke the deprecated bmad-dev-auto name, ensuring their requests reach bmad-build-auto and their old customization files are safely migrated. ## Core Features & Use Cases - Deprecation Redirect: Forwards any invocation of bmad-dev-auto to bmad-build-auto with the user's original input preserved verbatim. - Legacy File Migration: Detects bmad-dev-auto.toml and bmad-dev-auto.user.toml customization files and renames them to the bmad-build-auto equivalents only after explicit user approval. - Conflict Resolution: When both legacy and new files exist, compares their contents, proposes merged content, and halts safely if approval is declined. - Use Case: A user with an older BMAD setup types a bmad-dev-auto command; the Skill migrates their custom configuration and transparently runs bmad-build-auto instead. ## Quick Start Invoke bmad-dev-auto with your build request and it will redirect to bmad-build-auto after handling any legacy customization files.

Frequently Asked Questions about bmad-dev-auto

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

FAQPage Schema
How do I migrate from bmad-dev-auto to bmad-build-auto?

Invoke bmad-dev-auto as usual and it will detect legacy customization files, offer to rename them to bmad-build-auto equivalents, then forward your original input to bmad-build-auto. Going forward, invoke bmad-build-auto directly.

What happens to my bmad-dev-auto.toml customization file?

The Skill checks for bmad-dev-auto.toml and bmad-dev-auto.user.toml under _bmad/custom. If the new bmad-build-auto file does not exist, it offers to rename the legacy file after your explicit approval.

What if both old and new customization files exist?

The Skill reads both files, explains their differences, and proposes merged content for the new file. Only after you approve the content does it save the new file and remove the legacy one; otherwise it halts.

Why does bmad-dev-auto halt without running anything?

It halts when you decline a file rename or merge approval, when approval is unavailable, or when a file operation fails. This safety behavior prevents invoking bmad-build-auto with unmigrated or conflicting configuration.

Can I still use bmad-dev-auto permanently?

No, bmad-dev-auto is a deprecated shim that only forwards to bmad-build-auto. You should update your workflows and scripts to call bmad-build-auto directly.