bmad-create-architecture

Forwards legacy architecture creation invocations to bmad-architecture with create intent.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-architecture-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/3-solutioning/bmad-create-architecture
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-architecture-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing workflows and customization files that still invoke the deprecated bmad-create-architecture command, ensuring they continue to work while the BMAD framework transitions to the unified bmad-architecture skill. ## Core Features & Use Cases - Compatibility Shim: Resolves legacy TOML customization overrides (activation steps, persistent facts, on_complete hooks) and forwards them to bmad-architecture. - Deprecation Notice: Emits a localized warning guiding users to migrate their customization files to the new bmad-architecture format. - Use Case: A team with an existing _bmad/custom/bmad-create-architecture.toml file invokes the old skill name; this shim loads their overrides, warns about deprecation, and hands off to bmad-architecture with create intent so their architecture document workflow runs unchanged. ## Quick Start Invoke bmad-create-architecture as before and it will forward your request to bmad-architecture with create intent while applying your legacy customization overrides.

Frequently Asked Questions about bmad-create-architecture

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

FAQPage Schema
How do I migrate from bmad-create-architecture to bmad-architecture?▼

Rename your customization file from `_bmad/custom/bmad-create-architecture.toml` to `_bmad/custom/bmad-architecture.toml` and invoke bmad-architecture directly. Existing fields like activation_steps_prepend and persistent_facts remain supported, and the new version adds fields like spine_template and run_folder_pattern.

What happens when I invoke bmad-create-architecture now?▼

The skill resolves your legacy TOML overrides, loads the BMAD config for language settings, displays a deprecation notice, then forwards your original input to bmad-architecture with create intent. No further steps run in the shim itself.

Will my bmad-create-architecture.toml customizations still work?▼

Yes, the shim resolves legacy fields including activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete, then passes them to bmad-architecture. However, new customization fields are only available after migrating to bmad-architecture.toml.

When will bmad-create-architecture be removed?▼

According to the skill documentation, it will be removed in BMAD v7. It exists only as a compatibility shim, so new work should invoke bmad-architecture directly to avoid disruption.

Why does bmad-create-architecture show a deprecation notice?▼

The notice informs users the skill was consolidated into bmad-architecture and explains how to migrate customization files. It appears in the configured communication language and can be silenced by migrating to the new skill.