bmad-create-architecture

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-architecture-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-create-architecture
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-architecture-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing invocations of the deprecated bmad-create-architecture workflow, ensuring old commands and customization override files continue to work after consolidation into bmad-architecture. ## Core Features & Use Cases - Compatibility Shim: Resolves legacy TOML customization overrides (activation steps, persistent facts, on_complete hooks) and forwards them to bmad-architecture with create intent. - Deprecation Notice: Emits a localized notice 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 override invokes the old skill name; the shim loads their overrides, warns about deprecation, and hands off to bmad-architecture so the architecture document is still created as expected. ## Quick Start Invoke bmad-create-architecture to create a new architecture document and follow the migration notice to switch to bmad-architecture.

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 an architecture document with the BMad method?

Invoke bmad-architecture directly, which detects create, update, or validate intent from the conversation. The deprecated bmad-create-architecture skill 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 as a thin compatibility shim. Existing invocations by name and legacy TOML override files keep working, but it will be removed in a future release.

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

Yes, the shim resolves legacy fields like activation_steps_prepend, persistent_facts, and on_complete from your existing TOML file. Migrating to bmad-architecture.toml unlocks additional fields such as spine_template, doc_standards, and external_handoffs.

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 remain respected, and new customization options become available.

Why am I seeing a deprecation notice when creating architecture?

The notice appears because you invoked the deprecated bmad-create-architecture skill, which now forwards to bmad-architecture. Migrate your customization file and invoke bmad-architecture directly to silence the notice.