team-combat

Coordinate combat team members to design, implement, and validate a combat feature.

14|1|Updated Apr 12, 2026

Search Tags:#combat #design-automation #game-development #team-coordination #implementation-workflow

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill team-combat-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-combat
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/team-combat
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill team-combat-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill eliminates the fragmented hand‑off between designers, programmers, artists, and QA when building combat mechanics, ensuring a single, coherent workflow from concept to validated implementation.

Core Features & Use Cases

Design Orchestration: Guides a game designer to produce a detailed design document covering mechanics, formulas, and edge cases.
Architecture Validation: Engages an engine specialist to verify that the proposed code structure follows engine‑specific best practices.
Parallel Implementation: Executes gameplay, AI, VFX, and audio workstreams simultaneously, then integrates them.
Comprehensive Testing: Directs a QA tester to create test cases, run validations, and report performance impacts.
Use Cases: Ideal for creating features such as a melee parry system, ranged weapon spread, or any new combat mechanic requiring coordinated effort across the team.

Quick Start

Invoke the team-combat skill with a brief description of the combat feature you wish to develop.

Frequently Asked Questions about team-combat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate combat feature development across designers, programmers, artists, and QA?▼

Combat feature development across multiple disciplines can be coordinated using structured subagent prompts that guide design orchestration, architecture validation, parallel implementation, and comprehensive testing from concept to validated implementation.

What is the best way to manage parallel implementation workstreams for melee parry systems?▼

Parallel implementation for melee parry systems is best managed by simultaneously executing gameplay, AI, VFX, and audio workstreams, then integrating them to ensure a single coherent workflow without fragmented hand-offs.

How does architecture validation work for new combat mechanics in game development?▼

Architecture validation for combat mechanics works by engaging an engine specialist to verify that the proposed code structure follows engine-specific best practices before parallel implementation begins.

Can I use this workflow to create a design document covering combat formulas and edge cases?▼

Yes, you can use this workflow to create a detailed combat design document. Design orchestration guides a game designer to produce comprehensive documentation covering mechanics, formulas, and edge cases.

When do I need structured team coordination for implementing ranged weapon spread?▼

You need structured team coordination for ranged weapon spread when designers, programmers, artists, and QA must collaborate on mechanics, requiring design documents, parallel implementation tasks, and comprehensive testing to meet acceptance criteria.

What are the limitations of using design automation for combat feature implementation?▼

Design automation for combat features is limited by its reliance on structured subagent prompts and comprehensive testing; without proper architecture validation and parallel task integration, fragmented hand-offs between team members may still occur.