team-combat

Orchestrate multi-role game development pipelines for combat feature design and validation.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-combat-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-combat
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/team-combat
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-combat-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented, ad-hoc game development work by coordinating a full team to design, implement, and validate a combat feature in a single guided pipeline.

Core Features & Use Cases

  • End-to-end combat delivery: Runs a structured, phase-gated workflow from design through integration, validation, and sign-off.
  • Team orchestration for specialized roles: Delegates to a game designer, gameplay programmer, AI programmer, technical artist, sound designer, primary engine specialist, and QA tester.
  • User-approved phase transitions: Uses user selection via decisions at each transition to keep outcomes aligned with expectations.

Example use case: Create a melee parry system where formulas, edge cases, AI reactions, VFX/audio feedback, and QA test coverage are produced together and reviewed before implementation proceeds.

Quick Start

Tell the team to design and implement your combat feature by running /team-combat with a clear feature description like melee parry system or ranged weapon spread.

Frequently Asked Questions about team-combat

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

FAQPage Schema
How do I coordinate end-to-end combat feature delivery across multiple game development roles?▼

End-to-end combat feature delivery is orchestrated by coordinating specialized roles—gameplay programmer, AI programmer, technical artist, and QA tester—through a phase-gated pipeline from design to integration and validation.

What is a phase-gated pipeline for game AI and combat mechanics?▼

A phase-gated pipeline for combat mechanics is a structured workflow requiring user approval at each transition, ensuring design, engine architecture, AI behavior, and QA test planning align with expectations before proceeding.

How do I implement a melee parry system with AI reactions and VFX?▼

To implement a melee parry system, you coordinate gameplay logic, enemy AI reactions, VFX, audio feedback, and QA test coverage together, using a structured workflow to review formulas and edge cases before proceeding to integration.

Can I use phase gates to manage engine architecture validation and QA testing?▼

Yes, phase gates can manage engine architecture validation and QA testing by surfacing blocked agents with a partial completion report and requiring user approval before advancing to the next development phase.

What is the best way to structure game development workflows for action-combat mechanics?▼

The best way to structure game development workflows for action-combat mechanics is using a guided pipeline that delegates tasks to specialized roles, applying phase gates to validate engine-idiomatic architecture and gameplay logic before integration.

Why does my combat feature integration fail when gameplay logic and AI behavior are developed separately?▼

Combat feature integration fails when developed separately because ad-hoc work fragments the pipeline, whereas a coordinated workflow validates gameplay logic, enemy AI behavior, VFX, and audio together to prevent integration issues.