team-polish

Cross-team polish for a release involves orchestrating a structured workflow that aligns performance, visuals, audio, and QA teams to raise a feature to release-ready quality. The process uses subagents, structured handoffs, and gated decision points to track progress.

A structured polish workflow is a gated, task-driven process that delegates specialized tasks to subagents for performance analysis, technical art, sound design, and QA testing. It ensures a feature meets release standards through structured handoffs and risk-aware decision points.

Prepare a gameplay area for launch by running a cross-disciplinary polish workflow that optimizes performance, refines visuals, completes audio, and executes regression testing. The process applies risk-aware decision points to verify all areas meet quality standards.

Yes, you can use this workflow for post-iteration refinement after launch. The polish process applies to both preparation for launch and ongoing refinement of features, gameplay areas, or UI modules to maintain quality standards.

Yes, the workflow handles handoffs between technical artists and QA testers through structured task delegation. It assigns specific tasks to subagents representing each discipline and uses gated decision points to manage transitions between teams.

Avoid using a cross-team polish workflow for minor fixes or single-discipline tasks that do not require coordinated performance, visual, audio, and QA efforts. The workflow is designed for complex features requiring structured handoffs and multi-team coordination.