team-combat

To build a combat feature end-to-end, you can orchestrate cross-disciplinary roles like game-designer, gameplay-programmer, and qa-tester across defined design, architecture, and validation phases. This ensures structured delegation and tracked documentation throughout the project lifecycle.

Managing game design documentation alongside AI programming requires a phase-driven workflow that produces design docs, architecture sketches, and test plans. Explicit decision points and user approvals ensure alignment between technical artists, sound designers, and programmers during integration.

This agent orchestration workflow is designed for full combat feature development where cross-disciplinary collaboration is required. It assigns roles like ai-programmer, technical-artist, and sound-designer, making it most suitable for comprehensive projects needing structured delegation rather than isolated tasks.

Phase-based decision making works by defining explicit design, architecture, implementation, integration, and validation stages. User approvals are required at decision points before progressing, ensuring that deliverables from gameplay programmers and QA testers meet acceptance criteria.

Yes, team coordination includes documentation governance that ensures design docs, architecture sketches, test plans, and acceptance criteria are produced and tracked across the feature lifecycle by the qa-tester and other assigned subagents.