team-polish

A cross-functional polish cycle coordinates performance, accessibility, animation, QA, and content review teams in parallel to harden a feature for release. It aggregates findings into a unified backlog with owners, priorities, and acceptance criteria.

A feature polish plan surfaces gaps across performance, accessibility, QA, and content disciplines by loading PRDs and design assets. It prioritizes fixes and generates a consolidated backlog with risk gate artifacts for stakeholder sign-off.

Running parallel performance and accessibility reviews requires orchestrating specialized reviewers against the current implementation. The process aggregates findings into a gated readiness check to ensure release quality standards are met.

Yes, team-orchestration for quality assurance operates within a specific feature or area context. By providing a feature name, it loads relevant PRDs and implementation details to generate a consolidated polish report and backlog.

Generating release readiness artifacts is best handled by orchestrating five specialized reviewers in parallel. This aggregates cross-functional findings into a polished artifact suite, including a risk gate and traceability records for sign-off.

A multi-disciplinary polish cycle requires an existing feature context with loaded PRDs and design assets to function effectively. Without current implementation details, it cannot accurately surface gaps or prioritize fixes across the required disciplines.