bmad-create-architecture

Name: bmad-create-architecture
Availability: InStock
Author: Marc

Forward legacy create-intent requests to the bmad-architecture engine.

Updated Jul 11, 2026

Search Tags:#automation #workflow #architecture #documentation #migration #deprecation

Ready to run

npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-architecture-marcmontecalvo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-architecture
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-create-architecture
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-architecture-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a legacy compatibility layer for generating architectural documentation, ensuring that existing automated workflows continue to function while transitioning to the updated bmad-architecture system.

Core Features & Use Cases

Compatibility Shim: Automatically forwards legacy create-intent requests to the modern bmad-architecture engine.
Customization Preservation: Respects existing legacy configuration files and persistent facts during the transition period.
Use Case: Use this if you have existing automated pipelines or override files that specifically invoke the bmad-create-architecture command and you are not yet ready to migrate to the new architecture command.

Quick Start

Invoke the bmad-create-architecture skill with your project requirements to initiate the architectural design process.

Frequently Asked Questions about bmad-create-architecture

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

FAQPage Schema

How do I maintain automated architectural documentation workflows during a system migration?▼

A compatibility shim maps legacy architectural generation inputs to a modern engine, preserving persistent facts and existing customization fields to ensure continuity during transition periods.

When do I need a compatibility layer for architectural documentation generation?▼

You need this compatibility layer when you have existing automated pipelines or override files invoking legacy commands and are not yet ready to migrate directly to the updated architecture engine.

Does the legacy architecture creation workflow preserve existing configuration files?▼

Yes, the workflow respects existing legacy configuration files and persistent facts during the transition, ensuring automated pipelines continue functioning without losing custom settings.

How do I transition automated architecture generation tasks to a unified system?▼

Transition automated architecture generation tasks by mapping legacy inputs to a current architecture engine through a compatibility layer, which forwards requests while maintaining existing customization fields for continuity.

What are the limitations of using a deprecated architecture creation workflow?▼

The limitation is that this deprecated workflow acts only as a transitional compatibility shim, meaning you should eventually migrate directly to the new architecture command for full feature support.