bmad-quick-dev

Redirects deprecated bmad-quick-dev invocations to bmad-build with legacy config migration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents breakage when users or workflows still invoke the deprecated bmad-quick-dev name, ensuring requests are forwarded to bmad-build and old customization files are migrated safely. ## Core Features & Use Cases - Deprecation Redirect: Detects invocation of the legacy skill name and forwards the user's original input verbatim to bmad-build exactly once. - Legacy Config Migration: Finds bmad-quick-dev.toml and bmad-quick-dev.user.toml customization files and renames them to their bmad-build equivalents only after explicit user approval. - Conflict Resolution: When both old and new config files exist, compares them, explains differences, and merges values with user confirmation before removing the legacy file. - Use Case: A team upgrades their BMAD installation and an old automation still calls bmad-quick-dev; this shim migrates their customization files and routes the request to bmad-build without losing settings. ## Quick Start Invoke bmad-quick-dev with your build request and follow the prompts to migrate any legacy customization files before being redirected to bmad-build.

Frequently Asked Questions about bmad-quick-dev

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

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

Invoke bmad-quick-dev once and it handles the migration automatically. It detects legacy customization files, offers to rename them to bmad-build equivalents, and then forwards your original request to bmad-build.

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

The skill offers to rename bmad-quick-dev.toml to bmad-build.toml, but only after your explicit approval. If you decline or the rename fails, it halts without invoking any skill, leaving your files untouched.

What if both bmad-quick-dev.toml and bmad-build.toml already exist?

The skill reads both files, explains their differences, and proposes merged content for the new file. It resolves conflicting values with you and only saves and removes the legacy file after your explicit approval.

Should I still use bmad-quick-dev in new workflows?

No, bmad-quick-dev is deprecated and should not be used unless invoked by its legacy name. Update your workflows and scripts to call bmad-build directly to avoid the redirect shim.

Why does bmad-quick-dev halt without doing anything?

It halts when you decline a file rename, approval is unavailable, or a file operation fails. This is a safety measure to prevent overwriting or losing your customization settings without consent.