game-skill-orchestration

Game Skill Orchestration

Core Workflow

1. Classify the request by outcome, not by keywords alone: prototype, production feature, design doc, creative direction, review, refactor, asset plan, implementation, validation, or pitch.
2. Select the smallest useful set of game skills. Combine skills only when the work genuinely crosses discipline boundaries.
3. Write an outcome-first brief before detailed work when the task is broad:
   • Desired player experience
   • Concrete deliverable
   • Target platform/engine
   • Constraints and allowed side effects
   • Acceptance criteria
   • Evidence or validation required
   • Open questions that materially affect the outcome
4. Route domain work to the relevant skill references, then synthesize decisions into one coherent plan or artifact.
5. Define validation depth based on risk: concept sanity check, checklist review, prototype test, playtest script, technical test, performance check, accessibility review, or production-readiness review.
6. Keep outputs compact and structured. Use tables, checklists, and short specs when they make decisions easier to compare.

Cross-Skill Support

• Use product-brainstorming-planning before this skill when the game idea is vague, exploratory, or not yet ready for a feature brief.
• Use game-playtesting-usability when design decisions need player evidence, usability findings, difficulty feedback, onboarding clarity, or playtest reports.
• Use experiment-design-validation when a game feature, onboarding change, monetization idea, or retention hypothesis should be tested before broad rollout.
• Use customer-research-validation when a game audience, player motivation, or demand assumption needs structured research.
• Use competitive-market-research when genre, competitor, pricing, Steam/itch page, feature, or market-positioning evidence should inform decisions.
• Use accessibility-inclusive-design when game UI, controls, subtitles, motion, difficulty assists, remapping, or inclusive play needs accessibility review.
• Use pricing-packaging-strategy when monetization, DLC, tiers, subscriptions, donations, pay-what-you-want, or storefront pricing needs structured pricing decisions.
• Use product-analytics-instrumentation when game telemetry, funnels, onboarding/retention metrics, playtest instrumentation, event taxonomy, or analytics QA is needed.
• Use qa-test-strategy when game release quality, regression coverage, platform/device coverage, compatibility, or acceptance gates need structure.
• Use release-launch-readiness when publishing, launch, rollout, rollback, support, monitoring, or post-launch review needs coordination.
• Use visual-ui-ux-audit with game-ui-design, game-threejs-development, or game-phaser-development when browser screenshots or interactive states should drive critique.
• Use react-next-performance-optimization when a web-based game shell, landing page, editor, dashboard, or launcher uses React/Next.js.
• Use concise-technical-writing for compact game design docs, changelogs, release notes, itch.io page copy, PR summaries, and implementation summaries.
• Use skill-evaluation-iteration when improving the game skillset itself or testing whether a game skill changes output quality.