What problem does it solve?
This Skill solves the disjointed, error-prone process of building game combat features by coordinating specialized cross-functional roles, eliminating misalignment between design, implementation, art, audio, and QA teams that leads to unbalanced mechanics, bugs, and delayed releases.
Core Features & Use Cases
- Structured 6-Phase Pipeline: End-to-end workflow covering design, architecture, implementation, integration, validation, and sign-off, with mandatory user approval at each phase transition to maintain alignment.
- Parallel Cross-Functional Orchestration: Spawns specialized subagents (game designers, programmers, technical artists, sound designers, QA) to work concurrently on independent tasks, reducing development time for combat features.
- Use Case: Build a new melee parry system: the game designer defines mechanic rules and edge cases, the gameplay programmer implements core code, the technical artist creates parry VFX, the sound designer adds impact audio, and QA validates edge cases like parrying multiple sequential attacks.
Quick Start
Invoke the team-combat skill with a clear description of the combat feature you want to develop, such as 'design and implement a melee parry system with directional input and counterattack windows'.