원클릭으로
team-polish
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.
메뉴
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.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
| name | team-polish |
| description | 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. |
| argument-hint | [feature or area to polish] [--review full|lean|solo] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite |
| model | sonnet |
If no argument is provided, output usage guidance and exit without spawning any agents:
Usage:
/team-polish [feature or area]— specify the feature or area to polish (e.g.,combat,main menu,inventory system,level-1). Do not useAskUserQuestionhere; output the guidance directly.
When this skill is invoked with an argument, orchestrate the polish team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
--review [mode] was passed as an argument, use that mode.production/review-mode.txt — use whatever is written there.lean.Modes:
full — spawn all director and lead gates as describedlean — skip director gates unless they are PHASE-GATE type (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)solo — skip all director gate spawning entirely; run the skill without any agent gatesStore the resolved mode for use in all subsequent phases.
Director gate skip rule: Before spawning any Tier 1 director or lead for review (outside of PHASE-GATE triggers), apply the resolved mode: skip if solo mode; skip if lean mode and this is not a PHASE-GATE.
Use the Task tool to spawn each team member as a subagent:
subagent_type: performance-analyst — Profiling, optimization, memory analysissubagent_type: engine-programmer — Engine-level fixes for rendering, memory, resource loadingsubagent_type: technical-artist — VFX polish, shader optimization, visual qualitysubagent_type: sound-designer — Audio polish, mixing, ambient layerssubagent_type: tools-programmer — Content pipeline and editor tool verificationsubagent_type: qa-tester — Edge case testing, regression testing, soak testingAlways 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).
Delegate to performance-analyst:
/perf-profileDelegate to performance-analyst (with relevant programmers as needed):
If Phase 1 identified engine-level root causes (rendering pipeline, resource loading, memory allocator), delegate those fixes to engine-programmer in parallel:
Delegate to technical-artist:
Delegate to sound-designer:
Delegate to qa-tester:
If any spawned agent (via Task) returns BLOCKED, errors, or cannot complete:
Common blockers:
/architecture-decision first/create-storiesAll file writes (performance reports, test results, evidence docs) are delegated to sub-agents spawned via Task. Each sub-agent enforces the "May I write to [path]?" protocol. This orchestrator does not write files directly.
A summary report covering: performance before/after metrics, visual polish changes, audio polish changes, test results, and release readiness assessment.
/release-checklist for the final pre-release validation./sprint-plan update and re-run /team-polish after fixes./gate-check for a formal phase gate verdict before handing off to release.