When this skill is invoked, orchestrate the polish team through a structured pipeline.
Team Composition
- performance-analyst — Profiling, optimization, memory analysis, frame budget
- technical-artist — VFX polish, shader optimization, visual quality
- sound-designer — Audio polish, mixing, ambient layers, feedback sounds
- qa-tester — Edge case testing, regression testing, soak testing
How to Delegate
Use the Task tool to spawn each team member as a subagent:
subagent_type: performance-analyst — Profiling, optimization, memory analysissubagent_type: technical-artist — VFX polish, shader optimization, visual qualitysubagent_type: sound-designer — Audio polish, mixing, ambient layerssubagent_type: qa-tester — Edge case testing, regression testing, soak testing
Always provide full context in each agent's prompt (target feature/area, performance budgets, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phases 3 and 4 can run simultaneously).
Pipeline
Phase 1: Assessment
Delegate to performance-analyst:
- Profile the target feature/area using
/perf-profile
- Identify performance bottlenecks and frame budget violations
- Measure memory usage and check for leaks
- Benchmark against target hardware specs
- Output: performance report with prioritized optimization list
Phase 2: Optimization
Delegate to performance-analyst (with relevant programmers as needed):
- Fix performance hotspots identified in Phase 1
- Optimize draw calls, reduce overdraw
- Fix memory leaks and reduce allocation pressure
- Verify optimizations don't change gameplay behavior
- Output: optimized code with before/after metrics
Phase 3: Visual Polish (parallel with Phase 2)
Delegate to technical-artist:
- Review VFX for quality and consistency with art bible
- Optimize particle systems and shader effects
- Add screen shake, camera effects, and visual juice where appropriate
- Ensure effects degrade gracefully on lower settings
- Output: polished visual effects
Phase 4: Audio Polish (parallel with Phase 2)
Delegate to sound-designer:
- Review audio events for completeness (are any actions missing sound feedback?)
- Check audio mix levels — nothing too loud or too quiet relative to the mix
- Add ambient audio layers for atmosphere
- Verify audio plays correctly with spatial positioning
- Output: audio polish list and mixing notes
Phase 5: Hardening
Delegate to qa-tester:
- Test all edge cases: boundary conditions, rapid inputs, unusual sequences
- Soak test: run the feature for extended periods checking for degradation
- Stress test: maximum entities, worst-case scenarios
- Regression test: verify polish changes haven't broken existing functionality
- Test on minimum spec hardware (if available)
- Output: test results with any remaining issues
Phase 6: Sign-off
- Collect results from all team members
- Compare performance metrics against budgets
- Report: READY FOR RELEASE / NEEDS MORE WORK
- List any remaining issues with severity and recommendations
Output
A summary report covering: performance before/after metrics, visual polish changes, audio polish changes, test results, and release readiness assessment.
1---2name: team-polish3description: Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.4---5When this skill is invoked, orchestrate the polish team through a structured pipeline.
6
7## Team Composition
8- **performance-analyst** — Profiling, optimization, memory analysis, frame budget
9- **technical-artist** — VFX polish, shader optimization, visual quality
10- **sound-designer** — Audio polish, mixing, ambient layers, feedback sounds
11- **qa-tester** — Edge case testing, regression testing, soak testing
12
13## How to Delegate
14
15Use the Task tool to spawn each team member as a subagent:
16- `subagent_type: performance-analyst` — Profiling, optimization, memory analysis
17- `subagent_type: technical-artist` — VFX polish, shader optimization, visual quality
18- `subagent_type: sound-designer` — Audio polish, mixing, ambient layers
19- `subagent_type: qa-tester` — Edge case testing, regression testing, soak testing
20
21Always provide full context in each agent's prompt (target feature/area, performance budgets, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phases 3 and 4 can run simultaneously).
22
23## Pipeline
24
25### Phase 1: Assessment
26Delegate to **performance-analyst**:
27- Profile the target feature/area using `/perf-profile`
28- Identify performance bottlenecks and frame budget violations
29- Measure memory usage and check for leaks
30- Benchmark against target hardware specs
31- Output: performance report with prioritized optimization list
32
33### Phase 2: Optimization
34Delegate to **performance-analyst** (with relevant programmers as needed):
35- Fix performance hotspots identified in Phase 1
36- Optimize draw calls, reduce overdraw
37- Fix memory leaks and reduce allocation pressure
38- Verify optimizations don't change gameplay behavior
39- Output: optimized code with before/after metrics
40
41### Phase 3: Visual Polish (parallel with Phase 2)
42Delegate to **technical-artist**:
43- Review VFX for quality and consistency with art bible
44- Optimize particle systems and shader effects
45- Add screen shake, camera effects, and visual juice where appropriate
46- Ensure effects degrade gracefully on lower settings
47- Output: polished visual effects
48
49### Phase 4: Audio Polish (parallel with Phase 2)
50Delegate to **sound-designer**:
51- Review audio events for completeness (are any actions missing sound feedback?)
52- Check audio mix levels — nothing too loud or too quiet relative to the mix
53- Add ambient audio layers for atmosphere
54- Verify audio plays correctly with spatial positioning
55- Output: audio polish list and mixing notes
56
57### Phase 5: Hardening
58Delegate to **qa-tester**:
59- Test all edge cases: boundary conditions, rapid inputs, unusual sequences
60- Soak test: run the feature for extended periods checking for degradation
61- Stress test: maximum entities, worst-case scenarios
62- Regression test: verify polish changes haven't broken existing functionality
63- Test on minimum spec hardware (if available)
64- Output: test results with any remaining issues
65
66### Phase 6: Sign-off
67- Collect results from all team members
68- Compare performance metrics against budgets
69- Report: READY FOR RELEASE / NEEDS MORE WORK
70- List any remaining issues with severity and recommendations
71
72## Output
73A summary report covering: performance before/after metrics, visual polish changes, audio polish changes, test results, and release readiness assessment.
majiayu000