Orchestrate a phased multi-discipline polish pipeline for game features.
npx skills add https://github.com/scomofo/dragon-forge --skill team-polish-scomofo
Please help me install this Agent Skill. Skill: team-polish Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/team-polish Command: npx skills add https://github.com/scomofo/dragon-forge --skill team-polish-scomofo
It prevents features from slipping to release by organizing a focused, multi-discipline polish workflow that measures, improves, and regression-tests performance, visuals, audio, and stability.
Use Case: polish the "hatchery story-005 dragon unlock" area so it meets performance budgets, has consistent VFX/audio feedback, and passes edge-case and soak testing before release.
Use /team-polish hatchery --review lean to run a performance-first polish workflow with streamlined director gating while still covering the required QA and polish phases.
High-intent search queries and answers about installing and using this skill.
Game feature polish for release readiness is coordinated through a phased pipeline covering assessment, optimization, visual and audio polish, and QA hardening with regression and soak testing, using parallelized specialist delegation to profiling, engine, and technical art roles.
Performance profiling and VFX optimization before launch run best through an orchestrated multi-phase pipeline that assigns work to profiling and technical art specialists, followed by approval-gated phase transitions ensuring visual polish meets performance budgets.
Yes, review-mode governance supports full, lean, and solo orchestration with explicit gate-skipping rules, allowing you to streamline director gating for audio mixing and QA hardening while still covering required polish phases.
Subagent delegation handles blocked specialists using partial-result error recovery, allowing the orchestration pipeline to continue progressing through other disciplines like performance profiling or soak testing without halting the entire workflow.
Yes, YAML-defined skill metadata is required to control review-mode resolution and scope the phased subagent delegation for regression testing and soak testing during production development.
You should avoid a multi-discipline polish pipeline when a feature requires only isolated bug fixes rather than comprehensive performance, visual, audio, and stability hardening, as the orchestration overhead is designed for release-quality readiness across multiple areas.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
SjdjdiejdrirhdkjejPromote validated staging builds to production with semantic versioning and health checks.
wannasaynoneProfile CPU, GPU, memory, and load times to identify game performance bottlenecks.
imgamerOrchestrate cross-discipline review and hardening for a named game feature.
