team-combat

Coordinate multidisciplinary teams through phase-based combat feature design and validation workflows.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-combat-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-combat
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/team-combat
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-combat-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a multi-role team to design, implement, and validate a combat feature end-to-end, ensuring alignment, quality gates, and efficient collaboration across design, programming, AI, art, sound, and QA.

Core Features & Use Cases

  • Coordinated end-to-end workflow across roles
  • Phase-driven design, architecture, and validation
  • Clear delegation to specialized subagents with gated decisions

Quick Start

Provide a combat feature description after the command, for example 'melee parry system', to start the orchestration.

Frequently Asked Questions about team-combat

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

FAQPage Schema
How do I coordinate a combat feature workflow across multiple disciplines like design and programming?

Combat feature development requires orchestrating a multidisciplinary team across design, programming, AI, art, audio, and QA. This Skill coordinates the workflow using phase-based design, architecture, implementation, integration, and validation with gated approvals.

What is the best way to manage end-to-end game design implementation for a combat system?

End-to-end combat system implementation is managed by delegating tasks to specialized subagents via the Task tool. Decisions are captured through AskUserQuestion prompts, generating phase-specific artifacts to ensure alignment and quality gates.

Do I need structured prompts to start the engineering workflow for a melee combat feature?

Yes, structured prompts are required to initiate the engineering workflow. You provide a combat feature description, such as 'melee parry system', and the Skill orchestrates the team through subsequent phases requiring user approvals at each gate.

Can I use this orchestration process to validate AI and art assets for a combat feature?

Yes, the orchestration process applies to end-to-end feature validation, including AI and art assets. The Skill coordinates these multidisciplinary roles through dedicated phases, ensuring integration and quality validation before shipping.

Does the team coordination workflow support phase-based architecture decisions?

Yes, the team coordination workflow explicitly supports phase-based architecture. It drives feature design and implementation through structured phases, capturing architectural decisions as artifacts before proceeding to the next development stage.

What are the limitations of using a subagent-based design documentation workflow for game features?

The subagent-based design documentation workflow requires user approval at each phase gate, meaning development pauses until decisions are confirmed. It depends on the Task tool for delegation and structured prompts to generate phase-specific artifacts.