bmad-create-architecture

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing invocations of the retired bmad-create-architecture command, ensuring legacy override files and scripts keep working while routing all work to the consolidated bmad-architecture workflow. ## Core Features & Use Cases - Deprecation Forwarding: Emits a deprecation notice in the user's configured language and forwards the invocation to bmad-architecture with create intent. - Legacy Customization Resolution: Resolves legacy TOML overrides (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) via the resolve_customization.py script and passes them to the new workflow. - Use Case: A team with an existing _bmad/custom/bmad-create-architecture.toml file invokes the old skill name; the shim loads their overrides, warns them to migrate, and hands off to bmad-architecture without losing their configuration. ## Quick Start Invoke bmad-create-architecture as before and it will display a deprecation notice, then run the bmad-architecture workflow in create mode with your legacy customizations applied.

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 _bmad/custom/bmad-create-architecture.toml file to _bmad/custom/bmad-architecture.toml and invoke bmad-architecture directly. The new workflow detects create intent automatically and supports additional customization fields like spine_template and doc_standards.

What happens when I invoke the deprecated bmad-create-architecture skill?

The skill resolves your legacy TOML overrides, loads the bmm config for language settings, displays a deprecation notice, then invokes bmad-architecture with create intent. Your original input and legacy customizations are forwarded verbatim.

Will my bmad-create-architecture.toml overrides still work?

Yes, the four legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) are resolved and passed to bmad-architecture. Newer fields require migrating to bmad-architecture.toml.

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

The skill was consolidated into bmad-architecture, which now detects create, update, and validate intent from conversation. The notice informs you to migrate your customization file and invoke the new skill directly.

When will bmad-create-architecture be removed?

The documentation states it will be removed in a future release but gives no specific version. Migrate to bmad-architecture now to access the full customization surface and silence the notice.