bmad-quick-dev

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents breakage when users or workflows still invoke the retired bmad-quick-dev command, ensuring they are safely forwarded to bmad-build without losing their existing customization settings. ## Core Features & Use Cases - Deprecation Redirect: Detects invocation of the deprecated name and forwards the user's original input verbatim to bmad-build exactly once. - Legacy File Migration: Finds legacy customization files (bmad-quick-dev.toml and bmad-quick-dev.user.toml under _bmad/custom/) and renames them to their bmad-build equivalents only after explicit user approval. - Conflict Resolution: When both legacy and new files exist, compares their contents, explains differences, and merges values only with user confirmation, halting safely if approval is declined. - Use Case: A team upgraded their BMAD installation but still has old config files and muscle-memory commands; invoking bmad-quick-dev migrates their settings and transparently runs bmad-build instead. ## 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 input 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 after your explicit approval. If a bmad-build.toml already exists, it compares both files and proposes merged content instead of overwriting.

Can I still use bmad-quick-dev after the deprecation?

Yes, but only as a forwarding shim. It outputs a deprecation notice and invokes bmad-build exactly once with your original input, so you should update your workflows to call bmad-build directly.

What happens if I decline the file rename during migration?

The skill halts immediately and does not invoke bmad-build or any other skill. Your legacy files remain untouched, and no build action is taken until you approve the migration.

What if both legacy and new customization files exist?

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