bmad-create-architecture

Forwards legacy architecture creation invocations to the consolidated bmad-architecture workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and customization files still reference the retired bmad-create-architecture skill by name, and this compatibility shim keeps those invocations working while routing them to the consolidated bmad-architecture workflow. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy _bmad/custom/bmad-create-architecture.toml overrides so existing per-project customizations keep working. - Intent Forwarding: Invokes bmad-architecture with a fixed create intent, skipping its intent-detection step. - Deprecation Notice: Emits a localized notice guiding users to migrate their customization files to bmad-architecture.toml. - Use Case: A team with an older BMAD setup runs the legacy skill name; the shim loads their saved preferences, warns about deprecation, and hands off to the current architecture workflow without breaking their process. ## Quick Start Invoke the bmad-create-architecture skill by name 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 create a software architecture document with BMAD?

Invoke bmad-architecture directly, which detects create, update, or validate intent from your conversation. The legacy bmad-create-architecture name still works but simply forwards to bmad-architecture with create intent.

What happened to the bmad-create-architecture skill?

It was consolidated into bmad-architecture and retained only as a thin compatibility shim. It resolves legacy customization overrides, shows a deprecation notice, and forwards the request with create intent.

Will my bmad-create-architecture.toml customization file still work?

Yes, legacy fields like activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete are still resolved and passed through. Migrating to bmad-architecture.toml unlocks additional fields such as spine_template and doc_standards.

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 field values carry over, and new customization options become available.

Why am I seeing a deprecation notice when running this skill?

The notice appears because bmad-create-architecture is deprecated and forwards to bmad-architecture. To silence it, migrate your customization TOML to the bmad-architecture name and invoke that skill directly.