team-combat

You can coordinate a game development team for combat feature design by orchestrating cross-disciplinary roles like game design, programming, AI, art, sound, and QA through a phased pipeline. This approach assigns each discipline clear tasks and coordinates handoffs end-to-end.

Phase-driven delegation for combat systems is a coordination process that surfaces subagent proposals at each project phase and requires explicit user approval before proceeding. It ensures structured decision points across design, architecture, implementation, and validation artifacts.

To start a team-combat workflow for melee or ranged combat features, initiate the process by outlining the combat feature and following the phase-driven prompts to assign roles. These prompts guide the team through design, architecture, implementation, and validation.

Yes, cross-role orchestration is applicable when a game project requires coordinated design, architecture, implementation, and QA across multiple disciplines for either melee or ranged combat features. It generates artifacts including design docs, architecture sketches, code, tests, and validation plans.

End-to-end combat feature delivery involves game design, gameplay programming, AI programming, technical art, sound design, and QA testing. Each discipline receives a clear task within the phased pipeline, ensuring coordinated handoffs from initial design documentation to final validation.