team-combat

You can orchestrate a combat feature across game design, programming, and QA by using a structured pipeline with dedicated phases for design, architecture, implementation, integration, and validation. This coordinates multidisciplinary teams through formal review loops at each stage.

The best way to coordinate subagents for gameplay programming and AI behaviors is through dynamic work delegation with parallel execution where possible. This approach manages multidisciplinary tasks like NPC AI implementation while maintaining a formal review loop for each phase.

Yes, you can use this pipeline to design a melee parry system and integrate it with existing combat systems. It supports end-to-end implementation of combat features like melee parry, ranged weapon spread, and NPC AI behaviors across all development phases.

The error-recovery protocol handles blockers during combat system implementation by providing a structured response mechanism within the validation and integration phases. This ensures that multidisciplinary teams can address issues dynamically without halting the entire project management pipeline.

No additional dependencies are required to run the combat feature pipeline from design to sign-off. The workflow operates independently, coordinating team orchestration, role delegation via subagents, and phase reviews without external component requirements.

You should not use a multidisciplinary team orchestration pipeline for simple game development tasks that lack cross-functional requirements. This structured approach is designed for complex combat features requiring coordinated design, programming, art, audio, and QA phases.