bmad-dev-auto

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-dev-auto-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-auto
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-dev-auto
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-dev-auto-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents breakage when users still invoke the deprecated bmad-dev-auto name, ensuring their legacy customization files are safely migrated and their request is forwarded to the current bmad-build-auto skill. ## Core Features & Use Cases - Deprecation Redirect: Detects invocation of the old skill name and forwards the user's original input verbatim to bmad-build-auto exactly once. - Legacy File Migration: Finds 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 old and new customization files exist, it compares them, explains differences, and merges values with user confirmation before removing the legacy file. - Use Case: A user with an older BMAD setup types a bmad-dev-auto command; the skill migrates their config files and reruns their request through bmad-build-auto without losing customizations. ## Quick Start Invoke bmad-dev-auto with your original request and it will migrate any legacy customization files, then forward your input 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 once and it handles the migration automatically. It renames your legacy bmad-dev-auto.toml and bmad-dev-auto.user.toml files to the bmad-build-auto equivalents after your approval, then forwards your original request to bmad-build-auto.

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

The skill outputs a deprecation notice and redirects your exact input to bmad-build-auto. Before redirecting, it checks for legacy customization files and offers to migrate them so your settings are preserved.

What happens when both old and new BMAD customization files exist?

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

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

No. If the new file already exists, the skill never overwrites it. It compares both files, resolves conflicting values with you, and only saves changes after explicit approval.

What happens if I decline the file rename during migration?

The skill halts immediately and does not invoke bmad-build-auto or any other skill. Your legacy files remain untouched, and no further steps in the shim are executed.