team-polish

Orchestrate a six-role polish pipeline across design, technology, audio, and QA.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill team-polish-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-polish
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/team-polish
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill team-polish-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a cross-discipline polish pipeline to harden a feature for release quality by coordinating specialized roles across design, technology, audio, and QA.

Core Features & Use Cases

  • Structured six-role team: performance-analyst, godot-specialist, technical-artist, audio-director, tools-programmer, and qa-lead, each responsible for a dedicated polish domain.
  • Phase-based pipeline: assessment, optimization, visual polish, audio polish, hardening, and sign-off, with parallelization where possible.
  • Error recovery and governance: surface blockers immediately, offer options via guided decisions, and generate a partial final report when blocked.
  • Ready-for-release decision: aggregates results from all roles to determine readiness or the need for more work.

Quick Start

Invoke /team-polish with a target feature or area to polish to begin the orchestrated workflow.

Frequently Asked Questions about team-polish

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

FAQPage Schema
How do I coordinate game polish across gameplay, UI, and audio for a release-ready feature?

Coordinate game polish by running a phase-based pipeline that delegates specialized tasks to six subagents covering performance, Godot, technical art, audio, tools, and QA for release-ready features.

What is the best way to manage a cross-disciplinary polish pipeline for a Godot game?

The best way to manage a cross-disciplinary polish pipeline is using an orchestrated workflow that assigns dedicated domains to specialized roles, progressing through assessment, optimization, visual polish, audio polish, hardening, and sign-off.

Does this game release quality workflow support blocking issues during feature hardening?

Yes, the feature hardening workflow handles blocking issues by surfacing them immediately, offering guided decision options, and generating a partial final report when blocked to maintain release quality transparency.

How do I determine if a feature is ready for release after polish optimization?

Determine feature readiness for release by aggregating results from all subagent roles during a sign-off phase, which decides whether the feature passes approval gating or requires additional polish work.

Can I parallelize the game feature polish pipeline across different disciplines like art and audio?

Yes, you can parallelize the game feature polish pipeline across disciplines, allowing visual polish and audio polish phases to run concurrently while maintaining structured approval gating before release.

When should I use an orchestrated team pipeline for game feature polish instead of manual tracking?

Use an orchestrated team pipeline for game feature polish when a feature requires coordinated hardening across gameplay, UI, audio, and QA testing scope, making manual cross-disciplinary tracking inefficient and error-prone.