team-polish

Feature hardening for release readiness is coordinated by orchestrating performance analysis, visual polish, audio polish, content tooling verification, and QA edge-case testing into a single phase-gated pipeline with structured sign-off.

Visual polish and audio polish run in parallel with performance optimization using a phase-based delegation workflow, allowing simultaneous hardening of aesthetics and audio completeness alongside budget improvements before final QA testing.

Release quality orchestration uses phase-gated decision making by presenting interactive decision points where the user approves progression between phases based on subagent proposals and question-driven selectable options.

Yes, you can verify content tooling and test edge cases for a specific feature by invoking the skill with a feature argument, which triggers structured QA hardening and regression safety checks across the targeted area.

The final sign-off when hardening features for release provides a structured determination, outputting either READY FOR RELEASE or NEEDS MORE WORK based on the cumulative results of performance, aesthetic, audio, and QA phase approvals.

You need a dedicated polish workflow for performance budgets and aesthetic consistency when preparing a specific feature or area for release where regression safety, audio completeness, and visual rough edges must be resolved to avoid shipping risks.