bmad-dev-auto

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents breakage when users or workflows still invoke the deprecated bmad-dev-auto name, ensuring requests are safely forwarded to bmad-build-auto while legacy customization files are migrated instead of silently ignored. ## Core Features & Use Cases - Deprecation Redirect: Outputs a deprecation notice and forwards the user's original input verbatim to bmad-build-auto exactly once. - Legacy File Migration: Detects bmad-dev-auto.toml and bmad-dev-auto.user.toml under _bmad/custom and renames them to the bmad-build-auto equivalents only after explicit user approval. - Conflict Resolution: When both legacy and new files exist, reads both, explains differences, and merges values only with user confirmation, halting safely if approval is declined. - Use Case: A team upgrades their BMAD installation and an old automation still calls bmad-dev-auto; this shim migrates their customization files and routes the request to the new skill without losing configuration. ## Quick Start Invoke bmad-dev-auto with your original request and follow the prompts to approve renaming any legacy customization files before being redirected to bmad-build-auto.

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 before; it detects legacy customization files, offers to rename bmad-dev-auto.toml and bmad-dev-auto.user.toml to their bmad-build-auto equivalents, then forwards your original input to bmad-build-auto after migration completes.

What happens if I still call the deprecated bmad-dev-auto skill?

It prints a deprecation notice and invokes bmad-build-auto exactly once with your original input verbatim. If legacy customization files exist, it first walks you through renaming or merging them before redirecting.

What happens when both old and new customization files exist?

The skill reads both files, explains their differences, and proposes merged content for the new file. It saves and removes the legacy file only after your explicit approval; otherwise it halts without invoking any skill.

Will bmad-dev-auto overwrite my existing bmad-build-auto.toml?

No. If the new file already exists, it never overwrites it. Instead it compares both files, resolves conflicting values with you, and only writes the new file after you approve the exact proposed content.

What happens if I decline the file rename approval?

The skill halts immediately and does not invoke bmad-build-auto or any other skill. This prevents running with mismatched or unmigrated configuration until you explicitly approve the migration.