team-polish

Coordinate performance analysis, visual and audio polish, and QA verification toward release readiness.

1|Updated May 3, 2026

Search Tags:#performance optimization #orchestration #quality gates #visual polish #release readiness #qa testing #audio mixing

Ready to run

npx skills add https://github.com/imclab/xrA1-swarm --skill team-polish-imclab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-polish
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/team-polish
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill team-polish-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

team-polish eliminates the risk of shipping half-baked features by coordinating targeted specialists to optimize performance, improve audiovisual polish, and run structured QA hardening before release.

Core Features & Use Cases

Orchestrated polish pipeline: Runs a phase-based workflow from assessment to sign-off across performance, visuals, audio, and QA.
Parallel subagent delegation: Executes independent workstreams simultaneously (e.g., visual polish and audio polish alongside optimization).
User-gated decisions: Uses interactive approvals at phase transitions to ensure the user agrees with each proposal before proceeding.
Release readiness reporting: Produces a final READY FOR RELEASE / NEEDS MORE WORK verdict with remaining issues and recommendations.

Quick Start

Invoke team-polish with your target by saying: /team-polish combat.

Frequently Asked Questions about team-polish

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

FAQPage Schema

What is feature hardening for release readiness?▼

Feature hardening for release readiness is the process of coordinating performance analysis, visual and audio polish, and QA verification to turn features into release-quality work. It applies a structured multi-phase workflow to eliminate shipping half-baked features.

How do I orchestrate performance optimization and QA testing before a release?▼

You orchestrate performance optimization and QA testing by spawning parallel subagents per role to execute independent workstreams simultaneously. The workflow enforces phased user approvals via interactive questions at transitions, aggregating metrics before final sign-off gating.

Can I run visual polish and audio mixing workstreams at the same time?▼

Yes, you can run visual polish and audio mixing workstreams at the same time. The orchestration pipeline delegates independent refinement tasks to parallel subagents, executing them simultaneously alongside performance optimization to accelerate the hardening process.

What's the best way to gate feature releases with quality gates?▼

The best way to gate feature releases with quality gates is enforcing phased user approvals at workflow transitions. This interactive approach ensures you agree with each proposal before proceeding, culminating in a final release readiness assessment and sign-off.

Does release readiness reporting provide before and after performance metrics?▼

Yes, release readiness reporting provides before and after performance metrics. The final assessment aggregates performance metrics, polish changes, and QA results to produce a definitive READY FOR RELEASE or NEEDS MORE WORK verdict with remaining issues and recommendations.