bmad-agent-game-architect

The BMAD Game Architect workflow provides game design and architecture guidance using an AI agent. It routes user requests to the canonical gds-agent-game-architect skill, ensuring consistent behavior and operating style for game development sessions.

To invoke the BMAD Game Architect, simply request it by name. The system automatically routes your request to the canonical gds-agent-game-architect skill to maintain workflow continuity and deliver the expected game architecture behavior.

Yes, if the canonical gds-agent-game-architect skill is unavailable, the alias follows its own description and defers to the specified game-agent role. This fallback handling ensures the game architect workflow remains operational in your session.

Your request routes to the gds-agent-game-architect skill because this skill acts as a compatibility alias. It solves the problem by directing requests to the canonical skill to maintain consistent behavior without duplicating logic across the workflow.

Yes, you can use the alias for game design framework tasks. It uses the same game-agent framework, role, and operating style as the canonical skill, ensuring your game architecture workflow expectations are fully satisfied.

The alias does not duplicate the canonical skill's logic. If the canonical gds-agent-game-architect skill is unavailable, it relies on the alias description and game-agent role, which may offer reduced functionality compared to the full workflow.