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