team-polish

Cross-team polish work is coordinated by orchestrating a multi-role pipeline across assessment, optimization, visual polish, audio polish, hardening, and sign-off phases, capturing each phase output and requiring user approval before proceeding.

The feature polish pipeline delegates responsibilities to four subagents: performance-analyst for profiling, technical-artist for visual polish, sound-designer for audio polish, and qa-tester for hardening and verification.

To start the release-ready polish workflow, provide the target feature or area and initiate the pipeline to guide the coordinated team through all six phases toward a READY FOR RELEASE or NEEDS MORE WORK status.

Yes, the polish pipeline requires manual approval between phases. It applies explicit decision points guided by user input via AskUserQuestion to select proposals before proceeding to the next stage of feature hardening.

The best way to manage performance analysis and QA testing for release is to run them within a coordinated pipeline that captures phase outputs, maintains context, and culminates in a thorough verification sign-off.