bmad-agent-game-solo-dev

Route game solo development requests to the canonical gds-agent-game-solo-dev skill.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-agent-game-solo-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-game-solo-dev
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-agent-game-solo-dev
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-agent-game-solo-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This alias skill provides a compatibility bridge to the canonical gds-agent-game-solo-dev skill. It ensures you can invoke BMAD Game Solo Dev requests even if the primary skill is not loaded, by adopting the same role, operating style, and workflow expectations. If the canonical skill is available, it delegates to it.

Core Features & Use Cases

  • Alias compatibility: Reuses the canonical skill behavior when gds-agent-game-solo-dev is present.
  • Fallback behavior: Acts according to this alias description if the canonical skill is not loaded.
  • Role consistency: Maintains the same game-agent role and workflow as the canonical skill to minimize user disruption.

Quick Start

Ask this alias to route requests to the canonical gds-agent-game-solo-dev skill if available, otherwise perform the alias behavior as described.

Frequently Asked Questions about bmad-agent-game-solo-dev

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

FAQPage Schema
How do I use the BMAD game solo dev workflow when the canonical agent skill is not loaded?

The BMAD game solo dev workflow remains accessible through an alias skill that mimics the canonical agent's role, operating style, and workflow expectations, ensuring consistent behavior even when the primary skill is missing.

What is the purpose of an alias-ready agent workflow in game solo development?

An alias-ready agent workflow provides a compatibility bridge for game solo development, ensuring prompt requests are routed to the canonical skill when present and maintaining consistent functional behavior otherwise.

Does the BMAD game solo dev alias automatically delegate requests to the canonical skill?

Yes, the BMAD game solo dev alias automatically delegates requests to the canonical gds-agent-game-solo-dev skill when it is available in the session, satisfying functional consistency requirements.

Can I maintain consistent game-agent role behavior across sessions without the primary skill?

You can maintain consistent game-agent role behavior by using this alias skill, which adopts the same operating style and workflow expectations as the canonical skill to minimize user disruption.

What happens if the canonical gds-agent-game-solo-dev skill is missing during a game development session?

If the canonical gds-agent-game-solo-dev skill is missing, the alias performs fallback behavior by adopting the canonical skill's role and workflow, ensuring your game solo development prompts still execute correctly.