team-combat

To coordinate combat system development, you use a multi-stage pipeline with delegated subagents across design, implementation, and validation. It enforces structured decision points and design reviews to manage cross-functional teams from concept to finished product.

The end-to-end workflow for implementing a combat feature covers design, coding, asset creation, AI behavior, and QA. It uses delegated subagents and AskUserQuestion prompts to surface decisions at each stage before proceeding.

Managing design reviews during pipeline execution uses AskUserQuestion prompts that present optional approaches and require user approval before entering the next stage, ensuring structured validation throughout the combat feature lifecycle.

Yes, this pipeline applies to combat features requiring engine-compatibility checks and QA testing. It orchestrates validation steps across asset creation, AI behavior, and coding to ensure engine readiness before the finished product.

Team coordination for combat system development integrates design-docs within the initial design stage. Subagents handle design documentation before moving to implementation, ensuring all roles align on the combat feature concept.